Closed noga-dev closed 1 month ago
Have you configured docker for windows according to our docs https://supabase.com/docs/guides/cli/getting-started?
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?"
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.
This article was helpful. thank you
Helpful. Thanks
Thanks!! I was loosing my mind over this
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:
Expected behavior It's supposed to run normally like version 1.172.2
Screenshots [N/A]
System information
Additional context [N/A]