supabase
supabase_db_running-app container is not ready: unhealthy
Bug report [x] I confirm this is a bug with Supabase, not with my own application. [x] I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
When running supabase start, the command fails with the error:
supabase_db_running-app container is not ready: unhealthy
The local supabase setup doesn't start, preventing me from developing locally. I've already reinitialised the supabase folder with supabase init. Deleted all docker containers, volumes, and images but the same error keeps popping up when running supabase start.
FYI: The same thing happens when I try to do everything with npm.
To Reproduce
- Initialise an expo project with version 53.0.9
- Install supabase with brew →
brew install supabase/tap/supabase - Run
supabase init - Run
supabase start
Expected behavior The supabase start command should successfully start all required containers (database, API, Studio, etc.) and make the local development environment available without health check failures.
System information OS: macOS (Sequoia 15.2.0) Version of supabase-js: 2.50.0 Version of Node.js: v23.9.0 Version of Supabase CLI: 2.24.3 Version of Docker: 28.1.1
Can any one Look into this High Priority issue, as we are not able to run the Project locally, After Migrations the Docker Container is Getting unhealthy and after db reset , Container is Stopping!
im just upgrade my supabase cli and works fine. Is there some information about error in container log or service?
im just upgrade my supabase cli and works fine. Is there some information about error in container log or service?
Mmmh, I also just did (to 2.26.9). Though, I'm still facing the same issue. It's probably a me problem, but I'm really stuck on it, as I got not a single clue what could be causing it.
I already had uninstalled and reinstalled everything Docker related, etc.
@victorpergher what docker version are you running?
@timohuennebeck can you Check if this helps link
Thanks so much, man! That's exactly what worked for me. I just had to upgrade the Postgres Version in the Dashboard to 15.8.1.100.
Closing because of duplicate: https://github.com/supabase/cli/issues/3632#issuecomment-2934528135