[Bug]: ChromaDB Stateful Set permission denied error

[cmisale]

ChromaDB Version

0.4.x

Kubernetes Version

1.24.x

What happened?

Hi,

I am using the chromadb helm chart chromadb-0.1.23, image tag 0.6.3, on OpenShift.

I first had to update manually the generated template, because the base value doesn't go through. I am sharing the template in the issue.

Once I start the containers, I get the following error

$ kubectl logs chroma-chromadb-0
sed: couldn't open temporary file /chroma/sedBjGyZV: Permission denied

I launched a debug pod and that's how the inside looks like

1001030000@chroma-chromadb-0:/chroma$ ls -al
total 45
drwxr-xr-x. 1 chroma chroma        20 May 20 15:06 .
dr-xr-xr-x. 1 root   root          42 May 20 15:06 ..
-rwxr-xr-x. 1 chroma chroma       397 Feb 18 11:47 .dockerignore
-rwxr-xr-x. 1 chroma chroma     11357 Feb 18 11:47 LICENSE
-rwxr-xr-x. 1 chroma chroma      5255 Feb 18 11:47 README.md
drwxrwxrwx. 2     99         99  4096 May 20 14:25 chroma
drwxr-xr-x. 1 chroma chroma      4096 Feb 18 11:47 chromadb
-rw-r--r--. 1 root   1001030000   809 May 20 15:06 log_config.yaml
-rwxr-xr-x. 1 chroma chroma       187 Feb 18 11:47 main.py
-rwxr-xr-x. 1 chroma chroma      2140 Feb 18 11:47 pyproject.toml
-rwxr-xr-x. 1 chroma chroma       537 Feb 18 12:05 requirements.txt

I am attaching

• The result of helm template with my values.yaml. I manually edited the image name+tag because the bookworm string wasn't being added
• the values.yaml

Can anyone help?
Thanks a lot

template.yaml.txt
values.yaml.txt

Environment details

On-premises deployment of OpenShift 4.16

Logs, Kubectl output, Manifests, etc.

sed: couldn't open temporary file /chroma/sedBjGyZV: Permission denied

[tazarov]

@cmisale, I'll have a look at this today

[tazarov]

@cmisale, the issue specifically with 0.6.x images which were sourced from here https://github.com/amikos-tech/chroma-images. One of the goals for the images to be more robust by remove root access. The issue has to do with file perms as you've show

drwxrwxrwx. 2     99         99  4096 May 20 14:25 chroma
-rw-r--r--. 1 root   1001030000   809 May 20 15:06 log_config.yaml

As a simple solution I'll just revert to using Chroma core images from ghcr. I'll release a new version of the chart today.

[cmisale]

Got it, makes sense. Thanks a lot!