-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exec /docker_entrypoint.sh: no such file or directory[Install issue]: #1796
Comments
@crystal-yxj, do you mind sharing the command you use to create the container? Also which version of Chroma are you usign? |
I have same problem...
Versions |
Yes, same issue here |
Yes, I encountered the same issue as well. It took me about two days to find the solution... HaHa The reason for the issue varies between Windows and UNIX systems. Therefore, you will need to modify the Dockerfile from the original repository FROM python:3.11-slim-bookworm AS builder
ARG REBUILD_HNSWLIB
RUN apt-get update --fix-missing && apt-get install -y --fix-missing \
build-essential \
gcc \
g++ \
cmake \
autoconf && \
rm -rf /var/lib/apt/lists/* && \
mkdir /install
WORKDIR /install
COPY ./requirements.txt requirements.txt
RUN pip install --no-cache-dir --upgrade --prefix="/install" -r requirements.txt
RUN if [ "$REBUILD_HNSWLIB" = "true" ]; then pip install --no-binary :all: --force-reinstall --no-cache-dir --prefix="/install" chroma-hnswlib; fi
FROM python:3.11-slim-bookworm AS final
RUN mkdir /chroma
WORKDIR /chroma
COPY --from=builder /install /usr/local
COPY ./bin/docker_entrypoint.sh /docker_entrypoint.sh
COPY ./ /chroma
RUN apt-get update --fix-missing && apt-get install -y curl && \
chmod +x /docker_entrypoint.sh && \
rm -rf /var/lib/apt/lists/*
ENV CHROMA_HOST_ADDR "0.0.0.0"
ENV CHROMA_HOST_PORT 8000
ENV CHROMA_WORKERS 1
ENV CHROMA_LOG_CONFIG "chromadb/log_config.yml"
ENV CHROMA_TIMEOUT_KEEP_ALIVE 30
EXPOSE 8000
ENTRYPOINT ["/bin/bash", "-c", "uvicorn chromadb.app:app --workers ${CHROMA_WORKERS} --host ${CHROMA_HOST_ADDR} --port ${CHROMA_HOST_PORT} --proxy-headers --log-config ${CHROMA_LOG_CONFIG} --timeout-keep-alive ${CHROMA_TIMEOUT_KEEP_ALIVE}"] |
This is interesting, as all Chroma tests also run on Windows GH runner in docker, and we have not observed this particular problem. Reading the SO issue that @a868111817 shared, I get the feeling that the issue might be related to how the bash script is formatted. @a868111817, does this work for you as well: ENTRYPOINT ["/bin/bash", "-c","/docker_entrypoint.sh"]
CMD [ "--workers ${CHROMA_WORKERS} --host ${CHROMA_HOST_ADDR} --port ${CHROMA_HOST_PORT} --proxy-headers --log-config ${CHROMA_LOG_CONFIG} --timeout-keep-alive ${CHROMA_TIMEOUT_KEEP_ALIVE}"] |
Thank you for your response. I've tried your command, but I still believe the issue persists. |
Same issue here.
@a868111817 Thanks for your fix. |
@a868111817, I noticed you are running the |
What happened?
exec /docker_entrypoint.sh: no such file or directory
![image](https://private-user-images.githubusercontent.com/82490606/309172652-6f0aeca1-bb0e-411a-a163-970359ed9d82.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5MzM2MTgsIm5iZiI6MTcxOTkzMzMxOCwicGF0aCI6Ii84MjQ5MDYwNi8zMDkxNzI2NTItNmYwYWVjYTEtYmIwZS00MTFhLWExNjMtOTcwMzU5ZWQ5ZDgyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAyVDE1MTUxOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI1ODVjN2Y3OWY4Mzg4NmNlZWM2NTRmOWVlNDBkZGZjODhlZjdkZDhiYWU0NmI0MzI4OWUyNDc1NDcwMTY3ZTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.6ql8rvqZBgRbtlvSJOiv_tBCrQ2VZlRAkO0i1PoBXnk)
Versions
windows10
Relevant log output
No response
The text was updated successfully, but these errors were encountered: