-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[Install issue]: How to initialize the tenant and database when using a kubernetes cluster? #2502
Comments
@leobenkel, can you look up the error stack to see the actual error that you're getting from Chroma?
|
thank you for your response @tazarov ! here is the full log from the chroma docker:
I updaed my dockerfile to:
but im still able to
|
@leobenkel, this is weird: |
No no. I just redacted the log to not leak out a customer's name :) |
Indeed I did not create the tenant. Which is my original question in this post haha. I am asking how to initialize tenant and database. With the posgresql container I just had to set some environment variables. But I didn't find the equivalent for chromadb. |
@tazarov ? |
What happened?
So I am using chromadb docker image:
and i am hitting it from the other image.
the connection is working but then i am getting:
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 gettingWARNING: [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
The text was updated successfully, but these errors were encountered: