supabase_vector_project container is not ready: unhealthy

[noga-dev]

Describe the bug
I tried running supabase start using 1.183.5, 1.187.10, 1.187.14, I basically kept downgrading until I go to 1.172.2 which finally worked.

To Reproduce
Steps to reproduce the behavior:

1. Install any version in the last month.
2. Run 'supabase start'
3. Observe error "supabase_vector_project container is not ready: unhealthy"

Expected behavior
It's supposed to run normally like version 1.172.2

Screenshots
[N/A]

System information

• Ticket ID: 4f84685928bb4d429fa68bcf4803e93d
• Version of OS: Windows 11 x64
• Version of CLI: at least 1.183.5 and above (maybe lower I just started skipping more versions at once)
• Version of Docker: Docker Desktop 4.33.1 (161083)
• Versions of services:

   supabase/postgres      │ 15.1.1.78        │ -
   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.55.0          │ -
   supabase/studio        │ 20240729-ce42139 │ -
   supabase/postgres-meta │ v0.83.2          │ -
   supabase/logflare      │ 1.4.0            │ -
   supabase/supavisor     │ 1.1.56           │ -

Additional context
[N/A]

[sweatybridge]

Have you configured docker for windows according to our docs https://supabase.com/docs/guides/cli/getting-started?

[noga-dev]

Have you configured docker for windows according to our docs https://supabase.com/docs/guides/cli/getting-started?

Hmm, I see now, that the SS on that page shows that "Expose daemon on tcp://localhost:2375 without TLS" is supposed to be toggled on. And after doing so, I'm able to run Supabase on latest. But I don't want it turned on. Any way around this?

Also, shouldn't the error from the CLI be more useful than 'container is not ready: unhealthy?"

[sweatybridge]

We print a warning text in yellow. But it's probably drowned in the other logs.

If you don't want to turn on tcp daemon, you can turn off analytics as an alternative. Just set enabled = false in config.toml.

[thisisone]

This article was helpful.
thank you

[TallManCycles]

Helpful. Thanks

[douglas-yokomizo]

Thanks!! I was loosing my mind over this

[timrutter]

so i have this problem described above. I have tried enabling the daemon on the port, i have tried disabling the analytics but it still fails with 503 and then terminates everything. I'm using docker for windows.
Docker Desktop 4.34.3 (170107)
Windows 11
supabase 1.204.3
one thing that I did need to do was change all the ports as for some reason the ports are not available that are written in the toml file. Might this be a problem?

[sweatybridge]

@timrutter changing the port should be fine. Could you try the suggestion here #2753 (comment)

[islycodes]

Thanks! was very helpful.