This content originally appeared on DEV Community and was authored by Dave Mackey
This will be brief...
I ran into an issue using supabase start. It would get pretty far and then stop the containers due to a networking error.
I ended up finding an issue "supabase_vector_project container is not ready: unhealthy" in which noga-dev notes that enabling "Expose daemon on tcp://localhost:2375 without TLS" in Docker Desktop resolves the issue.
That is my experience as well.
I'm sure there is at least 1 other person in the world who will run into this issue...
This content originally appeared on DEV Community and was authored by Dave Mackey
Dave Mackey | Sciencx (2025-03-15T01:15:34+00:00) supabase_vector_project container is not ready: unhealthy. Retrieved from https://www.scien.cx/2025/03/15/supabase_vector_project-container-is-not-ready-unhealthy/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.