You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Running supabase start in my terminal fails to bring up the Supabase instance. After the health checks run for a while, all containers shut down automatically.
To Reproduce
Initialize a new project (e.g. supabase init).
In either a fresh or existing repo, run supabase start.
Wait a few seconds for the health checks to complete.
Expected behavior
Once the health checks finish, the CLI should display the URLs and JWT tokens for my application and Supabase Studio—just as it did until about two weeks ago.
System information
Ticket ID: 178ddacde57e4e5e97b2c3ff44eb6f00
Operating System: macOS 15.4.1
Supabase CLI: 2.22.6
Docker: 28.1.1
Service Versions:
SERVICE IMAGE
LOCAL
LINKED
supabase/postgres
15.8.1.069
–
supabase/gotrue
v2.171.0
–
postgrest/postgrest
v12.2.11
–
supabase/realtime
v2.34.47
–
supabase/storage-api
v1.22.6
–
supabase/edge-runtime
v1.67.4
–
supabase/studio
2025.04.21‑sha‑173cc56
–
supabase/postgres-meta
v0.88.9
–
supabase/logflare
1.12.0
–
supabase/supavisor
2.5.1
–
Additional context
Node.js: 23.11.0
The text was updated successfully, but these errors were encountered:
Describe the bug
Running
supabase start
in my terminal fails to bring up the Supabase instance. After the health checks run for a while, all containers shut down automatically.To Reproduce
Initialize a new project (e.g.
supabase init
).In either a fresh or existing repo, run
supabase start
.Wait a few seconds for the health checks to complete.
Expected behavior
Once the health checks finish, the CLI should display the URLs and JWT tokens for my application and Supabase Studio—just as it did until about two weeks ago.
System information
Ticket ID:
178ddacde57e4e5e97b2c3ff44eb6f00
Operating System: macOS 15.4.1
Supabase CLI: 2.22.6
Docker: 28.1.1
Service Versions:
Additional context
Node.js: 23.11.0
The text was updated successfully, but these errors were encountered: