Open sadihasanov opened 1 year ago
Are your running the 0.4.15 server too? This seems like you upgraded the client without upgrading the server
I believe server is running at 0.4.15. Just pushed the updated image today. I'll check in with the team to confirm this and come back to you
Can confirm
Python package: chromadb==0.4.15 Docker image: 0.4.15
Are you able to pull down the SQLite file from your DO instance and check to see if the table "tenants" is populated?
So I'm not sure if this is helpful but I got this error when i tried connecting to my database using the wrong port (for example, I had my docker port as 8001:8000 and was accidentally attempting to connect to 8000 instead of 8001)
What happened?
Hi everyone, I am not sure whether this is a bug but I couldn't find any information on this matter and its behavior is pretty weird.
I have my FastAPI app and I have a config file where I start the Chroma client and then just import it across the app. I use following method to connect the client:
client = chromadb.HttpClient(os.environ.get("VECTOR_DB_URL"), settings=Settings(chroma_client_auth_provider="chromadb.auth.token.TokenAuthClientProvider", chroma_client_auth_credentials=os.environ.get("VECTOR_DB_API_KEY")))
When I run it locally, it connects to Chroma that is hosted on DigitalOcean. When I try to run the docker image, I get the error.
If I go to vector_db_url/api/v1/heartbeat I get the response, so the link is valid and this error does not occur when running locally. Any ideas why this could be thrown and what is the solution?
Versions
Chroma 0.4.15
Relevant log output