Docker-chroma is being built for start-dev.sh
However, at this moment, the chroma release is broken - see https://github.com/chroma-core/chroma/issues/797.
This causes personids-lite not to function since when chroma does not work the plugin has an exception and the product is not working.
Moreover, the Dockerfile-chroma uses
RUN git clone https://github.com/chroma-core/chroma.git
so it takes the version that exists at the time of building, even if it is not the official version, simply the latest.
The production version takes it's image from personoids/chroma which is more stable, maybe the dev version should do the same since the dev version is probably for the personids-lite development and not for the chroma version. So taking it from the fixed version seems to avoid transient issues in the chroma development.
Docker-chroma is being built for start-dev.sh However, at this moment, the chroma release is broken - see https://github.com/chroma-core/chroma/issues/797. This causes personids-lite not to function since when chroma does not work the plugin has an exception and the product is not working.
Moreover, the Dockerfile-chroma uses
The production version takes it's image from personoids/chroma which is more stable, maybe the dev version should do the same since the dev version is probably for the personids-lite development and not for the chroma version. So taking it from the fixed version seems to avoid transient issues in the chroma development.