Self hosted Vector container fails to start #26362
Replies: 2 comments
-
For some reason, vector.yml gets created as a directory. You will need to remove vector.yml, and recreate it as a regular file. Then you will need to paste in the contents from this file in the Supabase GitHub. Lastly, you will need to remove the old supabase-vector docker volume, so docker doesn't complain that you're trying to mount a file to a directory. This can be done by running |
Beta Was this translation helpful? Give feedback.
-
I forgot to follow up - my issue was that the hosting machine had globally enabled usernamespace remapping for all containers https://docs.docker.com/engine/security/userns-remap which would not allow for bind mounts. Would be interesting to know if there was a best practice way to deploy supabase on such environments |
Beta Was this translation helpful? Give feedback.
-
I just cloned a fresh copy of supabase, pulled the images and ran
docker compose up
but the Vector container fails to start due toERROR vector::config::loading: Error opening config file. error=Permission denied (os error 13) path="etc/vector/vector.yml"
Running on a VPS
Debian 5.10.216-1 (2024-05-03) x86_64 GNU/Linux
usingDocker v26.1.2, build 211e74b
Any help is greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions