cli icon indicating copy to clipboard operation
cli copied to clipboard

supabase_vector_project container is not ready: unhealthy

Open Jonny1987 opened this issue 2 months ago • 0 comments

Describe the bug This error occurs when running supabase start with analytics enabled supabase_vector_project container is not ready: unhealthy

I was doing these steps in my comment on this closed issue which used to work but now doesn't: https://github.com/supabase/cli/issues/2588#issuecomment-3186001879

The suggestion on that issue just before it was closed does not help (only works for windows because that option in docker desktop does not exist on ubuntu) and it's not an option to just not have logs as they are important for development

To Reproduce Steps to reproduce the behavior:

  1. set enabled = true in the analytics section of config.toml
  2. Run supabase start

Expected behavior All containers start successfully

System information Rerun the failing command with --create-ticket flag. Note: supabase start --create-ticket doesn't show any different information

  • Version of OS: Ubuntu 22.04
  • Version of CLI: 2.65.5
  • Version of Docker: Docker version 28.3.2, build 578ccf6, docker desktop 4.55.0
  • Versions of services: SERVICE IMAGE | LOCAL | LINKED
    ------------------------|------------------------|------------ supabase/postgres | 15.6.1.113 | 15.6.1.113 supabase/gotrue | v2.184.0 | v2.184.0
    postgrest/postgrest | v12.2.3 | v12.2.3
    supabase/realtime | v2.67.2 | -
    supabase/storage-api | v1.32.1 | v1.31.1
    supabase/edge-runtime | v1.69.28 | -
    supabase/studio | 2025.12.01-sha-4ad48b7 | -
    supabase/postgres-meta | v0.93.1 | -
    supabase/logflare | 1.26.20 | -
    supabase/supavisor | 2.7.4 | -

Additional information

Logs from vector container:

2025-12-16T18:02:49.004094Z  INFO vector::app: Internal log rate limit configured. internal_log_rate_secs=10
2025-12-16T18:02:49.013103Z  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"
2025-12-16T18:02:49.016654Z  INFO vector::app: Loading configs. paths=["/etc/vector/vector.yaml"]
2025-12-16T18:02:49.107785Z  WARN vector::config::loading: Transform "router._unmatched" has no consumers
2025-12-16T18:02:49.113003Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::sources::docker_logs: Capturing logs from now on. now=2025-12-16T18:02:49.111905446+00:00
2025-12-16T18:02:49.116326Z  INFO source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::sources::docker_logs: Listening to docker log events.
2025-12-16T18:02:49.440851Z  INFO vector::topology::running: Running healthchecks.
2025-12-16T18:02:49.440965Z  INFO vector::topology::builder: Healthcheck passed.
2025-12-16T18:02:49.441028Z  INFO vector::topology::builder: Healthcheck passed.
2025-12-16T18:02:49.441050Z  INFO vector::topology::builder: Healthcheck passed.
2025-12-16T18:02:49.441056Z  INFO vector::topology::builder: Healthcheck passed.
2025-12-16T18:02:49.441062Z  INFO vector::topology::builder: Healthcheck passed.
2025-12-16T18:02:49.441067Z  INFO vector::topology::builder: Healthcheck passed.
2025-12-16T18:02:49.441073Z  INFO vector::topology::builder: Healthcheck passed.
2025-12-16T18:02:49.442615Z  INFO vector: Vector has started. debug="false" version="0.28.1" arch="x86_64" revision="ff15924 2023-03-06"
2025-12-16T18:02:49.449822Z ERROR source{component_kind="source" component_id=docker_host component_type=docker_logs component_name=docker_host}: vector::sources::docker_logs: Listing currently running containers failed. error=error trying to connect: Connection refused (os error 111)
2025-12-16T18:02:49.475864Z  INFO vector::internal_events::api: API server running. address=0.0.0.0:9001 playground=http://0.0.0.0:9001/playground
2025-12-16T18:02:49.475961Z  INFO vector::app: All sources have finished.
2025-12-16T18:02:49.475970Z  INFO vector: Vector has stopped.
2025-12-16T18:02:49.478199Z  INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="functions_logs, logflare_storage, kong_err, kong_logs, db_logs, rest_logs, project_logs, router, logflare_kong, storage_logs, realtime_logs, auth_logs, logflare_realtime, logflare_auth, logflare_rest, logflare_functions, logflare_db" time_remaining="59 seconds left"

Jonny1987 avatar Dec 16 '25 19:12 Jonny1987