cli: Vector fails to connect to docker socket on windows
Describe the bug
After update to v1.183.5, get this error when starting supabase cli: (local dev) … now downgraded back to 1.178.2, get these errors:
with downgraded v1.178.2
supabase_realtime_chat_app container logs:
21:30:04.267 [info] Migrations already up
21:30:05.018 [debug] QUERY OK db=1.8ms queue=140.7ms idle=0.0ms
begin []
21:30:05.043 [debug] QUERY ERROR source="tenants" db=0.0ms
SELECT t0."id", t0."name", t0."external_id", t0."jwt_secret", t0."jwt_jwks", t0."postgres_cdc_default", t0."max_concurrent_users", t0."max_events_per_second", t0."max_bytes_per_second", t0."max_channels_per_client", t0."max_joins_per_second", t0."suspend", t0."enable_authorization", t0."inserted_at", t0."updated_at" FROM "tenants" AS t0 WHERE (t0."external_id" = $1) ["realtime-dev"]
21:30:05.046 [debug] QUERY OK db=0.3ms
rollback []
** (Postgrex.Error) ERROR 42703 (undefined_column) column t0.enable_authorization does not exist
query: SELECT t0."id", t0."name", t0."external_id", t0."jwt_secret", t0."jwt_jwks", t0."postgres_cdc_default", t0."max_concurrent_users", t0."max_events_per_second", t0."max_bytes_per_second", t0."max_channels_per_client", t0."max_joins_per_second", t0."suspend", t0."enable_authorization", t0."inserted_at", t0."updated_at" FROM "tenants" AS t0 WHERE (t0."external_id" = $1)
(ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:932: Ecto.Adapters.SQL.raise_sql_call_error/1
(ecto_sql 3.8.3) lib/ecto/adapters/sql.ex:847: Ecto.Adapters.SQL.execute/6
(ecto 3.8.4) lib/ecto/repo/queryable.ex:221: Ecto.Repo.Queryable.execute/4
(ecto 3.8.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
(ecto 3.8.4) lib/ecto/repo/queryable.ex:147: Ecto.Repo.Queryable.one/3
/app/lib/realtime-2.28.32/priv/repo/seeds.exs:10: (file)
/app/lib/realtime-2.28.32/priv/repo/seeds.exs:9: (file)
nofile:1: (file)
.... repeats few times
Stopping containers...
supabase_realtime_chat_app container is not ready: unhealthy
with 1.183.5
WARNING: analytics requires mounting default docker socket: //./pipe/docker_engine
supabase_vector_chat_app container logs:
2024-07-09T21:46:56.683451Z INFO vector::app: Internal log rate limit configured. internal_log_rate_secs=10
2024-07-09T21:46:56.688088Z 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"
2024-07-09T21:46:56.691761Z INFO vector::app: Loading configs. paths=["/etc/vector/vector.yaml"]
2024-07-09T21:46:56.771891Z WARN vector::config::loading: Transform "router._unmatched" has no consumers
2024-07-09T21:46:56.777654Z 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=2024-07-09T21:46:56.776739985+00:00
2024-07-09T21:46:56.779760Z 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.
2024-07-09T21:46:56.943828Z INFO vector::topology::running: Running healthchecks.
2024-07-09T21:46:56.943905Z INFO vector::topology::builder: Healthcheck passed.
2024-07-09T21:46:56.943945Z INFO vector::topology::builder: Healthcheck passed.
2024-07-09T21:46:56.943965Z INFO vector::topology::builder: Healthcheck passed.
2024-07-09T21:46:56.943971Z INFO vector::topology::builder: Healthcheck passed.
2024-07-09T21:46:56.943975Z INFO vector::topology::builder: Healthcheck passed.
2024-07-09T21:46:56.943979Z INFO vector::topology::builder: Healthcheck passed.
2024-07-09T21:46:56.943983Z INFO vector::topology::builder: Healthcheck passed.
2024-07-09T21:46:56.944725Z INFO vector: Vector has started. debug="false" version="0.28.1" arch="x86_64" revision="ff15924 2023-03-06"
2024-07-09T21:46:56.951310Z 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)
2024-07-09T21:46:56.969415Z INFO vector::internal_events::api: API server running. address=0.0.0.0:9001 playground=http://0.0.0.0:9001/playground
2024-07-09T21:46:56.969467Z INFO vector::app: All sources have finished.
2024-07-09T21:46:56.969471Z INFO vector: Vector has stopped.
2024-07-09T21:46:56.972411Z INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="storage_logs, logflare_auth, realtime_logs, kong_logs, project_logs, logflare_kong, rest_logs, logflare_functions, db_logs, logflare_db, router, auth_logs, kong_err, logflare_storage, logflare_rest, logflare_realtime" time_remaining="59 seconds left"
... repeats a few times
Stopping containers...
supabase_vector_chat_app container is not ready: unhealthy
To Reproduce Steps to reproduce the behavior:
- Run ‘supabase start’
- See error above
Expected behavior
- No error and can continue running.
System information
- Ticket ID: tried with ‘–create-ticket’ flag, didn’t create any ticket number
- Version of OS: Windows 10
- Version of CLI: v1.183.5 and after downgrade to v1.178.2, problem still persists
- Version of Docker: v4.31.1
- Versions of services: with CLI v1.178.2
SERVICE IMAGE │ LOCAL │ LINKED
─────────────────────────┼──────────────────┼────────────
supabase/postgres │ 15.1.1.61 │ 15.1.1.61
supabase/gotrue │ v2.153.0 │ v2.153.0
postgrest/postgrest │ v12.1 │ v12.1
supabase/realtime │ v2.28.32 │ -
supabase/storage-api │ v1.6.8 │ v1.6.8
supabase/edge-runtime │ v1.54.6 │ -
supabase/studio │ 20240422-5cf8f30 │ -
supabase/postgres-meta │ v0.80.0 │ -
supabase/logflare │ 1.4.0 │ -
supabase/supavisor │ 1.1.56 │ -
darthsim/imgproxy │ v3.8.0 │ -
with CLI v1.183.5
SERVICE IMAGE │ LOCAL │ LINKED
─────────────────────────┼──────────────────┼────────────
supabase/postgres │ 15.1.1.61 │ 15.1.1.61
supabase/gotrue │ v2.153.0 │ v2.153.0
postgrest/postgrest │ v12.1 │ v12.1
supabase/realtime │ v2.29.15 │ -
supabase/storage-api │ v1.6.8 │ v1.6.8
supabase/edge-runtime │ v1.54.10 │ -
supabase/studio │ 20240701-05dfbec │ -
supabase/postgres-meta │ v0.83.2 │ -
supabase/logflare │ 1.4.0 │ -
supabase/supavisor │ 1.1.56 │ -
darthsim/imgproxy │ v3.8.0 │ -
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (3 by maintainers)
On 1.183.5, you want to disable analytics in config.toml since windows is not fully supported.
You can still use the docker desktop ui to view the logs.
Could “supabase start” detect if the host is Windows and automatically disable analytics? Otherwise is hard to know unless you find this.
Hi! I tested out on version
supabase: 2.12.1and still had the same error.No… don’t comment, set enabled = false
On version 1.187.10 it is still not working with the same error on windows. Deleting the previous volumes and containers also did not help.
It seems like I’m still having issues after making the changes to the docker config that you suggested. I am getting a different error message though. That said, I don’t really need analytics and am not an experienced docker user, so I may be missing other configuration settings that would resolve the issue. If you are wondering, this is what I am seeing still on my end:
Disabling analytics again resolves the problem. I tried restarting my system as well just in case the docker changes would only apply on reboot, but no luck. My supabase config file is the standard one save for disabling analytics, and my docker settings are the fresh install defaults save for the settings you recommended enabling to fix the issue.
still having the same problem on mac.
Agree with above that this needs to be more publicized. It was very difficult to find this (quite simple) solution to the problem, as when you run “supabase start” with the --debug flag as recommended by the command line, it gives an unrelated and unhelpful error of having a duplicate docker container name (something already named “supabase_res_Supabase”). Perhaps the supabase docs should be updated to note this required change to the config on Windows hosts until a solution is found?
In fact, looking at it now, the docs at https://supabase.com/docs/guides/cli/local-development actually say that logging is disabled by default, when it seems to actually be enabled by default now.
Confirmed to have the same problem and same solution on Supabase 2.12.1 with Windows 11 (10.0.22631 Build 22631, latest as of 22Feb2025)
This is the best answer. Disable analytics and you’ll be good.
new to supabase, just tried supabase start and getting same issue. this is with latest supabase running 1.190.0