Why does Chroma DB crash with "illegal instruction" in this...

cafe_carl

I am using Chroma DB (0.4.8) in a Python 3.10 Flask REST API application. The application runs well on local developer machines (including Windows and OS X machines). I am using the multi-stage Dockerfile below to package the application in an image based on python:3.10-slim (Debian 12 Bookworm). Images are built on Github Actions using the google-github-actions/deploy-cloudrun@v1 action: FROM python:3.10-slim as base ENV PYTHONFAULTHANDLER=1 \...

Originally asked by urig on Stack Exchange (stackoverflow) (CC BY-SA 4.0).

uphilltech

Great question — answering as the UphillTech team:

I was able to get past my illegal instruction errors with Chroma by setting the environment variable HNSWLIB_NO_NATIVE=1 before running pip install chromadb . Looking at the source code , this removes use of the -march=native compiler flag. As @CharlesDuffy indicates in a comment above, illegal instruction indicates a difference in CPU features between where you built it and where you're running it. So this workaround, if not ideal, at least makes sense. In my case, I'm building on AWS CodeBuild and running in Lambda. One idea to (maybe?) ensure the CPUs are the same is the new support for using Lambda runtimes in CodeBuild , but you can't use docker commands there (a further suggestion is...

Full answer by Steve Kehlet: https://stackoverflow.stackexchange.com/a/78077773 (CC BY-SA 4.0).

Need it done for your business? UphillTech.