[Bug]: ghcr.io/chroma-core/chroma does not support arm64 architecture

[jpmcb]

What happened?

On a M-chip Macbook, attempting to use chroma via the GitHub contaienr registry gives:

❯ docker run ghcr.io/chroma-core/chroma:0.4.5

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

It then attempts to rebuild some bits for the different architecture which looks like it's intentionally rebuilds some dependencies to support cross architecture.

Is it possible to support docker buildx in the container build?

chroma/bin/build

Line 3 in 6739259

docker build . --target chroma_server -t ghcr.io/chroma-core/chroma-server:`bin/version`

---

May also be related to #642 with some discussion of supporting arm images builds.

Versions

Chroma image 0.4.5

❯ uname -a
Darwin johns-mbp.lan 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:58 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6020 arm64

Relevant log output

No response

[jpmcb]

I was able to get this to work abit better with the following diff:

diff --git a/Dockerfile b/Dockerfile
index 489a6a96..f95c98f5 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,4 +1,6 @@
-FROM python:3.10-slim-bookworm as builder
+FROM --platform=$BUILDPLATFORM python:3.10-slim-bookworm as builder
+
+ARG BUILDPLATFORM

 RUN apt-get update --fix-missing && apt-get install -y --fix-missing \
     build-essential \
@@ -13,7 +15,9 @@ COPY ./requirements.txt requirements.txt

 RUN pip install --no-cache-dir --upgrade --prefix="/install" -r requirements.txt

-FROM python:3.10-slim-bookworm as final
+FROM --platform=$TARGETPLATFORM python:3.10-slim-bookworm as final
+
+ARG TARGETPLATFORM

 RUN apt-get update --fix-missing && apt-get install -y --fix-missing \
     build-essential \
diff --git a/bin/build b/bin/build
index 5e324198..ae908c4f 100755
--- a/bin/build
+++ b/bin/build
@@ -1,3 +1,3 @@
 #!/usr/bin/env bash

-docker build . --target chroma_server -t ghcr.io/chroma-core/chroma-server:`bin/version`
+docker buildx build --load . --target chroma_server -t ghcr.io/jpmcb/chroma-server:`bin/version`
diff --git a/bin/docker_entrypoint.sh b/bin/docker_entrypoint.sh
index 3b0d146c..afb672d7 100755
--- a/bin/docker_entrypoint.sh
+++ b/bin/docker_entrypoint.sh
@@ -1,6 +1,4 @@
 #!/bin/bash

-echo "Rebuilding hnsw to ensure architecture compatibility"
-pip install --force-reinstall --no-cache-dir chroma-hnswlib
 export IS_PERSISTENT=1
 uvicorn chromadb.app:app --workers 1 --host 0.0.0.0 --port 8000 --proxy-headers --log-config log_config.yml

Happy to open a PR.

Essentially this:

• Uses docker buildx to do cross image building. This also utilizes the BUILDPLATFORM and TARGETPLATFORM arguments for those builds in order to ensure the final cross image uses the target platform's architecture.
• Removes the re-building since that seems unnecessary for the cross architecture image

This was build with:

❯ docker buildx build \
            --tag=chroma-test:latest \
            --load \
            .

And I'm able to run it locally with:

❯ docker run -it --rm chroma-test
2023-08-12 15:26:44 INFO     chromadb.telemetry.posthog Anonymized telemetry enabled. See https://docs.trychroma.com/telemetry for more information.
2023-08-12 15:26:44 DEBUG    chromadb.config Starting component System
2023-08-12 15:26:44 DEBUG    chromadb.config Starting component Posthog
2023-08-12 15:26:44 DEBUG    chromadb.config Starting component SqliteDB
2023-08-12 15:26:44 DEBUG    chromadb.config Starting component LocalSegmentManager
2023-08-12 15:26:44 DEBUG    chromadb.config Starting component SegmentAPI
2023-08-12 15:26:44 INFO     uvicorn.error   Started server process [7]
2023-08-12 15:26:44 INFO     uvicorn.error   Waiting for application startup.
2023-08-12 15:26:44 INFO     uvicorn.error   Application startup complete.
2023-08-12 15:26:44 INFO     uvicorn.error   Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)

[HammadB]

I think #857 is addressing this

[jpmcb]

Nice! I'll give that change a try: thanks for pointing me to that!

Closed by #857

[HammadB]

@jpmcb Did that fix your issue?

[jeffchuber]

@jpmcb did this fix your issue?

[HammadB]

Closing as stale, I think #857 should address this