supabase: [Self Hosting] dependency failed to start: container supabase-vector is unhealthy
Bug report
- I confirm this is a bug with Supabase, not with my own application.
- I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
Self Hosting fail to start when docker compose is used.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Go to Gidpot machine’…’
- Choice the repository of supabase
- Open the project of supabase
- Navigate to docker directory
- Copy the .env.example to .env
- Run docker compose pull
- Run docker compose up
Expected behavior
Self Hosting start without problems
Screenshots
gitpod /workspace/supabase/docker (master) $ docker compose up
WARN[0000] The "MFA_ENABLED" variable is not set. Defaulting to a blank string.
[+] Running 13/12
✔ Network docker_default Created 0.9s
✔ Container supabase-vector Created 0.9s
✔ Container supabase-imgproxy Created 0.9s
✔ Container supabase-db Created 0.0s
✔ Container supabase-analytics Created 0.1s
✔ Container supabase-meta Created 0.1s
✔ Container supabase-auth Created 0.1s
✔ Container realtime-dev.supabase-realtime Created 0.1s
✔ Container supabase-kong Created 0.1s
✔ Container supabase-rest Created 0.1s
✔ Container supabase-edge-functions Created 0.1s
✔ Container supabase-studio Created 0.1s
✔ Container supabase-storage Created 0.0s
Attaching to realtime-dev.supabase-realtime, supabase-analytics, supabase-auth, supabase-db, supabase-edge-functions, supabase-imgproxy, supabase-kong, supabase-meta, supabase-rest, supabase-storage, supabase-studio, supabase-vector
supabase-imgproxy | WARNING [2023-08-24T12:11:46Z] No keys defined, so signature checking is disabled
supabase-imgproxy | WARNING [2023-08-24T12:11:46Z] No salts defined, so signature checking is disabled
supabase-imgproxy | WARNING [2023-08-24T12:11:46Z] Exposing root via IMGPROXY_LOCAL_FILESYSTEM_ROOT is unsafe
supabase-imgproxy | INFO [2023-08-24T12:11:46Z] Starting server at :5001
supabase-vector | 2023-08-24T12:11:47.154332Z INFO vector::app: Internal log rate limit configured. internal_log_rate_secs=10
supabase-vector | 2023-08-24T12:11:47.154623Z INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=trace,rdkafka=info,buffers=info,lapin=info,kube=info"
supabase-vector | 2023-08-24T12:11:47.154745Z INFO vector::app: Loading configs. paths=["etc/vector/vector.yml"]
supabase-vector | 2023-08-24T12:11:47.250136Z WARN vector::config::loading: Transform "kong_err" has no consumers
supabase-vector | 2023-08-24T12:11:47.250181Z WARN vector::config::loading: Transform "router._unmatched" has no consumers
supabase-vector | 2023-08-24T12:11:47.762198Z INFO vector::topology::running: Running healthchecks.
supabase-vector | 2023-08-24T12:11:47.762384Z INFO vector::topology::builder: Healthcheck passed.
supabase-vector | 2023-08-24T12:11:47.762414Z INFO vector::topology::builder: Healthcheck passed.
supabase-vector | 2023-08-24T12:11:47.762434Z INFO vector::topology::builder: Healthcheck passed.
supabase-vector | 2023-08-24T12:11:47.762443Z INFO vector::topology::builder: Healthcheck passed.
supabase-vector | 2023-08-24T12:11:47.762449Z INFO vector::topology::builder: Healthcheck passed.
supabase-vector | 2023-08-24T12:11:47.762460Z INFO vector::topology::builder: Healthcheck passed.
supabase-vector | 2023-08-24T12:11:47.762467Z INFO vector::topology::builder: Healthcheck passed.
supabase-vector | 2023-08-24T12:11:47.762696Z INFO vector: Vector has started. debug="false" version="0.28.1" arch="x86_64" revision="ff15924 2023-03-06"
supabase-vector | 2023-08-24T12:11:47.764148Z INFO source{component_kind="source" component_id=docker_syslog component_type=syslog component_name=docker_syslog}: vector::sources::util::net::tcp: Listening. addr=0.0.0.0:9000
supabase-vector | 2023-08-24T12:11:47.777645Z INFO vector::internal_events::api: API server running. address=0.0.0.0:9001 playground=http://0.0.0.0:9001/playground
supabase-imgproxy | INFO [2023-08-24T12:11:51Z] Started /health request_id=d4BpW0mW6y5ZsiibDq93x method=GET client_ip=127.0.0.1
supabase-imgproxy | INFO [2023-08-24T12:11:51Z] Completed in 73.41µs /health request_id=d4BpW0mW6y5ZsiibDq93x method=GET status=200 client_ip=127.0.0.1
supabase-imgproxy | INFO [2023-08-24T12:11:57Z] Started /health request_id=uO8grDaxmu5EYDm5u2BTW method=GET client_ip=127.0.0.1
supabase-imgproxy | INFO [2023-08-24T12:11:57Z] Completed in 243.63µs /health request_id=uO8grDaxmu5EYDm5u2BTW method=GET status=200 client_ip=127.0.0.1
supabase-imgproxy | INFO [2023-08-24T12:12:03Z] Started /health request_id=g051Npsc73BC4yCeaBtMo method=GET client_ip=127.0.0.1
supabase-imgproxy | INFO [2023-08-24T12:12:03Z] Completed in 95.28µs /health request_id=g051Npsc73BC4yCeaBtMo method=GET status=200 client_ip=127.0.0.1
dependency failed to start: container supabase-vector is unhealthy
gitpod /workspace/supabase/docker (master) $
System information
- OS: Linux supabase-supabase-s84498vcpig 6.1.44-060144-generic #202308111259 SMP PREEMPT_DYNAMIC Fri Aug 11 14:20:00 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
- Docker: Docker version 24.0.5, build ced0996
Additional context
The instance is new and is default configuration
About this issue
- Original URL
- State: closed
- Created 10 months ago
- Reactions: 5
- Comments: 21 (1 by maintainers)
For me, doing a
sudo docker compose restartsolved the issue.After checking out changes from #17122 , I was able to get it running by adding
VECTOR_API_PORT=9001to my .env filesame error
Solution
Linux/MacOS:
sudo docker compose restartWindows:
run cmd as administrator (via right click)THIS! Got the same error and doing a compose restart was the only solution that worked.
I don’t think it’s a solution, but a hotfix.
Maybe this ticket should be reopened again
I am facing the same issue for a self hosted supabase. Some more backgrund info:
When starting with
docker compose upstartup fails:Despite this, supabase is running well except for logflare (which depends on supabase-vector, so this makes sense).
As for the others above, running
docker compose restartseems to work, as there is no error shown:But actually when running
docker psit becomse obvious that supabase-vector is still not running.:Does anybody have the idea, where the problem is coming from?
I run into this issue, too.
I am not sure, what was about the vector, but I did nothing special, just the typical microsoft method: switch off and on and off and on.
+1
But i realized that vector container is not working and showing
docker psafter restart. This is really headache when someone is touching first supabase. Creating several droplets to try different variants. Resizing but eventuallydocker psis not responding. Url freezing, sorry its not good welcoming… Going away to alternatives, best for all