Supabase dev service no longer starting, vector container keeps restarting

[sosensible]

Describe the bug Using supabase cli to do local dev. The start fails with the vector container restarting until healthcheck fails.

To Reproduce Steps to reproduce the behavior:

1. run > supabase start ... in project that was working
2. starts until the vector container quits, starts, quits, starts, ... health check fail
3. failed running this also, still attempted health check > supabase start --ignore-health-check

Expected behavior Supabase services to start local like they used to.

Screenshots n/a

System information Rerun the failing command with --create-ticket flag.

• Ticket ID: e8fd446f149a4b67aab8ce16d71549fa
• Version of OS: Windows 11
• Version of CLI: 1.183.5
• Version of Docker: 27.0.3
• Versions of services:

      SERVICE IMAGE      │      LOCAL       │ LINKED
  ─────────────────────────┼──────────────────┼─────────
  supabase/postgres      │ 15.1.1.61        │ -
  supabase/gotrue        │ v2.151.0         │ -
  postgrest/postgrest    │ v12.2.0          │ -
  supabase/realtime      │ v2.29.15         │ -
  supabase/storage-api   │ v1.0.6           │ -
  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           │ -

  Additional context n/a

[sosensible]

I use Docker for multiple things; nothing else has been an issue ATM or recently.

[hemanshum]

I'm experiencing the same issue when trying to start it on Windows; however, it works fine on Mac.

[sweatybridge]

The workaround for now is to turn off analytics in config.toml

[analytics]
enabled = false

[sweatybridge]

I've tested a fix for this in cli 1.187.5. You will need to enable a few settings on docker desktop on windows (see screenshot).

• expose daemon on tcp
• allow *.docker.internal names

After that, you can enable analytics without running into crashloop. The postgres and api gateway logs are still unavailable on studio but I will look into that separately. https://github.com/supabase/supabase/issues/26785

[sosensible]

This should be reopened, it did not fix things. I created the setting above.

• config.toml > analytics false
• set the docker settings you outlined

The local supabase starts, and in less than a minute, after pulling current images. It is not showing the vector DB restarting, now it just fails the healthcheck perhaps, but the flag to ignore healthcheck had no impact. Still failed.

P.S. We used scoop to install supabase and are running on the current update.

[sweatybridge]

@sosensible the fix is only released to beta channel atm. Could you give npx supabase@beta start a try?

[jorgeguberte]

@sweatybridge that worked for me. I also enabled the settings in Docker. Thank you!

[SebasScript]

supabase@beta is working on windows 11. Thanks for for updates!

[sosensible]

For us, supabase@beta is not working on Windows 11. Everything starts up, and with or without the ignore health check flag, it still shuts right down after everything starts up.

[jdgamble555]

I'm getting this issue again in Supabase 1.191.3.

[Mohsen7s]

I'm getting this issue again in Supabase 1.191.3.

Confirmed on my Windows 11 machine. supabase --version 1.191.3 EDIT: I have applied requested docker configs above : expose daemon on tcp allow *.docker.internal names

The same error and crashloop happens. Please re-open issue

[1WorldCapture]

supabase@beta works for me only when I set "analytics=false", in this way vector container will not be started.