-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
What happened?
So I am using chromadb docker image:
ARG VECTOR_DB_ENGINE_VERSION
FROM chromadb/chroma:${VECTOR_DB_ENGINE_VERSION}
ENV IS_PERSISTENT=true
ENV PERSIST_DIRECTORY=/chroma/chroma
ENV ANONYMIZED_TELEMETRY=false
ENV CHROMA_SERVER_NOFILE=4096
ENV CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER="chromadb.auth.token.TokenConfigServerAuthCredentialsProvider"
ENV CHROMA_SERVER_AUTH_PROVIDER="chromadb.auth.token.TokenAuthServerProvider"
ENV CHROMA_CLIENT_AUTH_PROVIDER="chromadb.auth.token_authn.TokenAuthClientProvider"
ARG VECTOR_DB_HEADER_TOKEN_TRANSPORT
ENV CHROMA_SERVER_AUTH_TOKEN_TRANSPORT_HEADER=VECTOR_DB_HEADER_TOKEN_TRANSPORT
ENV CHROMA_AUTH_TOKEN_TRANSPORT_HEADER=VECTOR_DB_HEADER_TOKEN_TRANSPORT
ARG VECTOR_DB_HEADER_AUTH_CREDS
ENV CHROMA_SERVER_AUTH_CREDENTIALS=VECTOR_DB_HEADER_AUTH_CREDS
ENV CHROMA_CLIENT_AUTH_CREDENTIALS=VECTOR_DB_HEADER_AUTH_CREDS
EXPOSE 8000
COPY chroma_log_config.yml /chroma/chromadb/log_config.yml
and i am hitting it from the other image.
the connection is working but then i am getting:
ValueError: Could not connect to tenant <tenant>. Are you sure it exists?
When I did the same process for posgresql, I just had to add few ENV variable in the db dockerfile to match the back-end ones.
I have been searching for few hours and I dont see how to do the same thing for chromadb. How do i setup the tenant / database names to match between the two services ?
Thank you !
Also, does ANONYMIZED_TELEMETRY=false turn off telemetry ? or keep on just not anonymized ? I want telemetry completely off.
Also, it seems the auth token is not working as expected. i am able to hit chroma without token and get something back.
Also, it seems CHROMA_SERVER_NOFILE is not doing anything. I am still getting WARNING: [11-07-2024 10:57:13] chroma_server_nofile is set to 65535, but this is less than current soft limit of 1048576. chroma_server_nofile will not be set. in the log.
Versions
docker image: 0.5.4
Relevant log output
No response