[Install issue]: cannot create new collection on vm in gcp

[valentingoelz]

What happened?

I set up a VM on gcp with your terraform templates in the deployment examples. The VM is up and running and I can get a heartbeat, but when I try to create a new collection with my HttpClient no id is created, thus the call fails. The collection is still created but without an id, rendering it useless.

Versions

Chroma v0.4.5, Python 3.10, Mac

Relevant log output

Traceback (most recent call last):
  File "/Users/acc/Documents/repo/our_repo/nova/scripts/chroma_second_test.py", line 10, in <module>
    collection = client.create_collection("test4")
  File "/Users/acc/Documents/repo/our_repo/.venv/lib/python3.10/site-packages/chromadb/api/fastapi.py", line 92, in create_collection
    id=resp_json["id"],
KeyError: 'id'

Process finished with exit code 1

[tazarov]

@Bl4ckEnd, not sure if you have noticed that the TF template uses chroma 0.3.14 whereas you mention you use chroma client 0.4.5 - https://github.com/chroma-core/chroma/blob/221bdfa91335bb096fbc632f098a858ff56ea866/examples/deployments/google-cloud-compute/startup.sh#L22C4-L22C45

If you can update the TF to use the latest version of chroma however you have to observe that the latest docker-compose does not rely on clickhouse anymore.

@jeffchuber @HammadB I think we can update the TF template to reflect the latest version of chroma

[HammadB]

Yes, we need to update the terraform @tazarov - is that something you would be up for?

[tazarov]

@HammadB, sure, assign this to me.

[tazarov]

@HammadB done and tested. Check the PR

[HammadB]

Amazing! Thank you :)

[tazarov]

@Bl4ckEnd now once the VM is started (takes about 5mins) everything seems to be working fine including creating a collection with HttpClient (0.4.5).

[tazarov]

@HammadB I think we can close this.

[HammadB]

Yep! Thanks. @Bl4ckEnd i think the underlying issue for you was client <> server version mismatch. @tazarov has kindly updated the TF to deploy the correct (or any) version of chroma so that should work now.

We should probably not allow incompatible clients to communicate with the server. Closing this out but feel free to reopen if needed.