supabase_storage_api and supabase_studio_api containers are not ready: unhealthy

[Nariman-Fallahi]

Affected area

Local development

Supabase CLI version

2.111.0

Operating system

Manjaro Linux x64

Installation method

pnpm

Command

pnpm supabase start --debug

Actual output

Starting database...
Initialising schema...
Seeding globals from roles.sql...
WARN: no files matched pattern: supabase/seed.sql
Starting containers...
Waiting for health checks...
2026/08/07 12:48:28 HTTP HEAD: http://127.0.0.1:54321/rest-admin/v1/ready
2026/08/07 12:48:32 HTTP HEAD: http://127.0.0.1:54321/functions/v1/_internal/health
supabase_storage_api container logs:
supabase_studio_api container logs:
▲ Next.js 16.2.6
- Local:         http://localhost:3000
- Network:       http://0.0.0.0:3000
✓ Ready in 0ms
supabase_storage_api: container is not ready: unhealthy
supabase_studio_api: container is not ready: unhealthy

Expected behavior

I expected supabase start to start the local Supabase environment successfully, with all containers becoming healthy and ready without any health check failures.

Steps to reproduce

Steps to reproduce

1. Install Supabase CLI 2.111.0.

2. Open an existing Supabase project.

3. Run:

   pnpm supabase stop

4. Start the local Supabase environment with debug logging:

   pnpm supabase start --debug

5. Wait for the container health checks to complete.

6. Observe that the following containers remain unhealthy:

   supabase_storage_api: container is not ready: unhealthy
   supabase_studio_api: container is not ready: unhealthy
   

7. supabase start does not complete successfully.

Crash report ID

No response

Docker and service versions

### Docker version


Client:
 Version:           29.6.2
 API version:       1.55
 Go version:        go1.26.5-X:nodwarf5
 Git commit:        dfc4efb1e2
 Built:             Thu Jul 16 20:57:11 2026
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          29.6.2
  API version:      1.55 (minimum version 1.40)
  Go version:       go1.26.5-X:nodwarf5
  Git commit:       3d80467678
  Built:            Thu Jul 16 20:57:11 2026
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.3.3
  GitCommit:        aad11006b869517fcd3009450b6f82da282e1a9b.m
 runc:
  Version:          1.5.1
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0


### Supabase services


| SERVICE IMAGE          | LOCAL                  | LINKED |
| ---------------------- | ---------------------- | ------ |
| supabase/postgres      | 17.6.1.156             | -      |
| supabase/gotrue        | v2.194.0               | -      |
| postgrest/postgrest    | v14.15                 | -      |
| supabase/realtime      | v2.120.3               | -      |
| supabase/storage-api   | v1.67.20               | -      |
| supabase/edge-runtime  | v1.74.2                | -      |
| supabase/studio        | 2026.07.27-sha-cbb076d | -      |
| supabase/postgres-meta | v0.96.6                | -      |
| supabase/logflare      | 1.47.1                 | -      |
| supabase/supavisor     | 2.9.7                  | -      |

Additional context

No response

[avallete]

Hey there !

Could you try supabase stop --all --no-backup then supabase start ? This might be due to uncompatible services version with your local data.

This will reset your local data, so you want to back them up before if they're needed for your development.

[Nariman-Fallahi]

@avallete
Hi, I tried this, but the issue was not resolved. The problem still persists.