chroma icon indicating copy to clipboard operation
chroma copied to clipboard

Published 20 hours ago • verified publisher icon chroma-core

Docker server/client: data is lost on container restart

Open nicolasf opened this issue 1 year ago • 2 comments

Using the default docker deployment which is supposed to be disk persistent, after a restart I can't see any of the collections created before stopping the instance.

Reproducer:

  1. deploy chromadb with docker-compose (follow chroma's doc)
  2. connect to chromadb and create a collection
  3. check if the collection is there
  4. run docker-compose down and docker-compose up -d on chromadb's folder
  5. reconnect to chromadb and list collections: none will be there

nicolasf avatar Apr 02 '23 18:04 nicolasf

I don't seem to be able to find this doc, where did you read about it?

daanlenaerts avatar Apr 10 '23 14:04 daanlenaerts

https://docs.trychroma.com/usage-guide#running-chroma-in-clientserver-mode

nicolasf avatar Apr 10 '23 14:04 nicolasf

Same problem here. Not clear how to make it persistent while using JS client.

kamilmac avatar May 18 '23 08:05 kamilmac

@kamilmac the docker backend by defaults saves. You dont need to call .persist

jeffchuber avatar May 19 '23 04:05 jeffchuber

I believe this was addressed by this commit / PR https://github.com/chroma-core/chroma/commit/f02e41ade3f4c81816dfb7bdd590e2aaa65a34d5

jeffchuber avatar Jun 23 '23 17:06 jeffchuber