cli
cli copied to clipboard
supabase
Containers: postgres-meta and studio will not start on Docker Desktop 4.41.1 (191279) (MAC)
Describe the bug
Supabase CLI starts and runs all containers/services on Docker Desktop 4.40.0 (187762) as expected. After upgrading to Docker Desktop 4.41.1 (191279) the supabase start command starts most of the containers without fail but near the end of the startup process, prints the logs for supabase_pg_meta_dolphin-ir then the logs for supabase_studio_dolphin-ir then immediately stops all containers and reports the pg_meta container as unhealthy and studio as not ready. Watching the Docker Desktop Containers dashboard postgres-meta and studio never start. The postgres-meta volume does go green on the Images dashboard but studio does not.
To Reproduce
- Update to Docker Desktop 4.41.1 (191279)
- Verify settings, quit Docker Desktop, full reboot
- Start Docker Desktop and wait docker engine to start
- Run
supabase starton a known working project - See error:
supabase start --create-ticket
WARN: no SMS provider is enabled. Disabling phone login
WARNING: You are running different service versions locally than your linked project:
supabase/storage-api:v1.22.6 => v1.22.4
Run supabase link to update them.
WARNING: analytics requires mounting default docker socket: /var/run/docker.sock
supabase_pg_meta_dolphin-ir container logs:
{"level":"info","time":"2025-05-03T00:43:22.902Z","pid":1,"hostname":"6447abeb9142","msg":"Server listening at http://0.0.0.0:8080"}
{"level":"info","time":"2025-05-03T00:43:22.910Z","pid":1,"hostname":"6447abeb9142","msg":"Server listening at http://0.0.0.0:8081"}
supabase_studio_dolphin-ir container logs:
▲ Next.js 14.2.26
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
▲ Next.js 14.2.26
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
✓ Ready in 1421ms
Stopping containers...
supabase_pg_meta_dolphin-ir container is not ready: unhealthy
supabase_studio_dolphin-ir container is not ready: starting
Try rerunning the command with --debug to troubleshoot the error.
Sent crash report: b17d028f771a460789ffb87641d3f18a
Expected behavior
I downgraded to back to the previous version and supabase start works as expected.
The same project on the previous Docker Desktop 4.40.0 (187762)
supabase start
WARN: no SMS provider is enabled. Disabling phone login
WARNING: You are running different service versions locally than your linked project:
supabase/storage-api:v1.22.6 => v1.22.4
Run supabase link to update them.
WARNING: analytics requires mounting default docker socket: /var/run/docker.sock
Started supabase local development setup.
API URL: http://127.0.0.1:54321
GraphQL URL: http://127.0.0.1:54321/graphql/v1
S3 Storage URL: http://127.0.0.1:54321/storage/v1/s3
DB URL: postgresql://postgres:[email protected]:54322/postgres
Studio URL: http://127.0.0.1:54323
Inbucket URL: http://127.0.0.1:54324
JWT secret: super-secret-jwt-token-with-at-least-32-characters-long
anon key: xxx
service_role key: xxx
S3 Access Key: xxx
S3 Secret Key: xxx
S3 Region: local
I upgraded to Docker Desktop 4.41.1 (191279) again and the issue returned.
Screenshots These settings are the same on both versions of Docker Desktop:
This is the version that, when updated to, causes the failure.
System information
- Ticket ID: b17d028f771a460789ffb87641d3f18a
- Version of OS: Sequoia 15.4 (24E248)
- Version of CLI: 2.22.6
- Version of Docker: v28.1.1, build 4eba377 - Docker Desktop 4.41.1 build 191279
- Versions of services:
SERVICE IMAGE | LOCAL | LINKED
------------------------|------------------------|------------ supabase/postgres | 15.8.1.079 | 15.8.1.079 supabase/gotrue | v2.171.0 | v2.171.0
postgrest/postgrest | v12.2.3 | v12.2.3
supabase/realtime | v2.34.47 | -
supabase/storage-api | v1.22.6 | v1.22.4
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
- Browser: NA
- Version of supabase-js: NA
- Version of Node.js: v22.14.0
Additional testing
- To isolate the issue I also tried creating a new project with
supabase bootstrapwith the same result. - I also tried this entire Docker Desktop upgrade/downgrade process three known working projects on a MacPro running Sequoia 15.4.1 (24E263) with the same results.
- I also tried upgrading the cli to
supabase/tap/supabase-betawith no success. - I have just downgraded for now as I cannot come up with a workaround or fix.
- For anyone else experiencing this issue, as of the time I created this issue, the version available for download is still the working v4.40.0 here. If it happens to be updated I can share a copy of the v4.40.0 dmg I have.
The Issue:
After upgrading to the newest version of Docker, I am unable to run the command npx supabase start successfully.
I keep getting the same error on Docker Version 4.41.2 (191736) as the issue: https://github.com/supabase/cli/issues/3512#issue-3037062246
Environment
- MacOS 15.4.1
- Docker Desktop for Mac (Intel)
- Ticket ID: a691d3efeaf94e2dba2f5414cfa2ca4c
> npx supabase start
supabase_analytics_my-app container logs:
supabase_realtime_my-app container logs:
1048576
Running migrations
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
00:03:18.871 [info] Migrations already up
+ '[' true = true ']'
+ echo 'Seeding selfhosted Realtime'
Seeding selfhosted Realtime
+ sudo -E -u nobody /app/bin/realtime eval 'Realtime.Release.seeds(Realtime.Repo)'
Starting Realtime
1048576
+ echo 'Starting Realtime'
+ ulimit -n
+ exec /app/bin/server
supabase_storage_my-app container logs:
supabase_pg_meta_my-app container logs:
{"level":"info","time":"2025-05-08T00:03:49.612Z","pid":1,"hostname":"476b7107bd8f","msg":"Server listening at http://0.0.0.0:8080"}
{"level":"info","time":"2025-05-08T00:03:49.647Z","pid":1,"hostname":"476b7107bd8f","msg":"Server listening at http://0.0.0.0:8081"}
supabase_studio_my-app container logs:
▲ Next.js 15.3.1
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
▲ Next.js 15.3.1
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
▲ Next.js 15.3.1
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
▲ Next.js 15.3.1
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
Stopping containers...
supabase_analytics_my-app container is not ready: unhealthy
supabase_realtime_my-app container is not ready: unhealthy
supabase_storage_my-app container is not ready: unhealthy
supabase_pg_meta_my-app container is not ready: unhealthy
supabase_studio_my-app container is not ready: starting
Try rerunning the command with --debug to troubleshoot the error.
Docker Version 4.41.1 (191279) (Getting the same error)
>> npx supabase start --create-ticket
15.8.1.069: Pulling from supabase/postgres
9d80e2a452b8: Pulling fs layer
fefc40e3c53b: Pulling fs layer
fd4f3265edd3: Pulling fs layer
31ebd585bb3d: Pulling fs layer
d9802f032d67: Pulling fs layer
08a58c943492: Pulling fs layer
3fcc160c69f1: Pulling fs layer
96117480ad4b: Pulling fs layer
4f4fb700ef54: Pulling fs layer
dab41ca7e30a: Pulling fs layer
29b90f929459: Pulling fs layer
cdbe83134b80: Pulling fs layer
71f7a15b17fa: Pulling fs layer
c798c3dc160d: Pulling fs layer
8aaf2b0d81b8: Pulling fs layer
9d80e2a452b8: Pull complete
e2a4519414ad: Pull complete
e961ae3d9fbf: Pull complete
4e5f9d7bf71d: Pull complete
b5f5b1a172d6: Pull complete
af0dbe20a13d: Pull complete
f0e08031e2fd: Pull complete
e1ff5e548a41: Pull complete
75b8e47a7546: Pull complete
56d325757d5c: Pull complete
6fb48f83a16a: Pull complete
5e78907865ad: Pull complete
12e841106921: Pull complete
1dcf59721d23: Pull complete
4f059c11bff4: Pull complete
4ba5570cad10: Pull complete
26913d4e89a8: Pull complete
0d9b85bd6163: Pull complete
78cde049af84: Pull complete
30c5d67dbc9b: Pull complete
d4daba49664e: Pull complete
fbd74e9bdaea: Pull complete
29b599b582d0: Pull complete
3a71105511b5: Pull complete
8975b9922b6b: Pull complete
fd8272c48e89: Pull complete
2aea65486e4f: Pull complete
4a968f10383d: Pull complete
a15ef2724f05: Pull complete
a15ee614e7e4: Pull complete
cd6f35e0d0b0: Pull complete
Digest: sha256:bfcc409fb3d4b46ac4a224bbd969e74224a408a7d42a572990567d4a88147a9c
Status: Downloaded newer image for public.ecr.aws/supabase/postgres:15.8.1.069
v2.34.47: Pulling from supabase/realtime
4f4fb700ef54: Pull complete
0235ccf3603c: Pull complete
555e909c17d9: Pull complete
9dbf1c6ca43d: Pull complete
2d429b9e73a6: Pull complete
d621c9960bf9: Pull complete
5b46285220ee: Pull complete
2e977104dcdb: Pull complete
Digest: sha256:4d2460cb6eb081b7cfec0e6b0af57f547497f60cf897621555303992d299f6e8
Status: Downloaded newer image for public.ecr.aws/supabase/realtime:v2.34.47
v1.22.11: Pulling from supabase/storage-api
f18232174bc9: Pull complete
4509b69886a5: Pull complete
63786652eaff: Pull complete
551866dfa045: Pull complete
10997caf18b1: Pull complete
0c2b42acd277: Pull complete
71b77f045319: Pull complete
5ea095f2c886: Pull complete
88886aa05fe3: Pull complete
dbe19fa58562: Pull complete
Digest: sha256:1ec825b3be75bb7170edbc919e4310489ec72bf533aacee4ed1aedf3b45aa357
Status: Downloaded newer image for public.ecr.aws/supabase/storage-api:v1.22.11
v2.171.0: Pulling from supabase/gotrue
66d4adc0d78a: Pull complete
482559462259: Pull complete
783193c7e859: Pull complete
ef3ae84fadfe: Pull complete
5b90554c318f: Pull complete
Digest: sha256:884f1a203a6a999251492d3d7092a4077b714ef210650a85f338a84385093ea4
Status: Downloaded newer image for public.ecr.aws/supabase/gotrue:v2.171.0
Seeding globals from roles.sql...
WARN: no files matched pattern: supabase/seed.sql
1.12.0: Pulling from supabase/logflare
36466221e163: Pull complete
6ee86da401ed: Pull complete
6dce3b49cfe6: Pull complete
e75a1d4ede51: Pull complete
3cd949345fce: Pull complete
4f4fb700ef54: Pull complete
0355fee61241: Pull complete
67383e6273a2: Pull complete
e0a5f96a9640: Pull complete
0c0938cbe80b: Pull complete
Digest: sha256:84d0cda731e1fe43c24531003660c7f5e82c460b80b48493041701381ec0eeee
Status: Downloaded newer image for public.ecr.aws/supabase/logflare:1.12.0
WARNING: analytics requires mounting default docker socket: /var/run/docker.sock
0.28.1-alpine: Pulling from supabase/vector
6bbeea27f58c: Pull complete
2b092e92b1a0: Pull complete
9ced58d1ef15: Pull complete
d261077062b2: Pull complete
4f4fb700ef54: Pull complete
2babd04ec7b1: Pull complete
Digest: sha256:4bc04aca94a44f04b427a490f346e7397ef7ce61fe589d718f744f7d92cb5c80
Status: Downloaded newer image for public.ecr.aws/supabase/vector:0.28.1-alpine
2.8.1: Pulling from supabase/kong
814dd06d26c7: Pull complete
213ec9aee27d: Pull complete
a70653f7a2d5: Pull complete
531e3bd93090: Pull complete
Digest: sha256:1b53405d8680a09d6f44494b7990bf7da2ea43f84a258c59717d4539abf09f6d
Status: Downloaded newer image for public.ecr.aws/supabase/kong:2.8.1
v1.22.3: Pulling from supabase/mailpit
900bac0c57cc: Pull complete
fe2636d02863: Pull complete
Digest: sha256:f7f7c31de4de59540ad6515a0ca057a77525bca2069b6e747d873ca66c10fe08
Status: Downloaded newer image for public.ecr.aws/supabase/mailpit:v1.22.3
v12.2.12: Pulling from supabase/postgrest
a839b31a073f: Pull complete
Digest: sha256:5f4ce744539bbba786b4e24dbbd95bdb2a956dcf568c5374995a0ff4a68f5bd2
Status: Downloaded newer image for public.ecr.aws/supabase/postgrest:v12.2.12
v1.67.4: Pulling from supabase/edge-runtime
126586508cfc: Pull complete
6e909acdb790: Pull complete
3956f985b675: Pull complete
8a05c7f45a2f: Pull complete
e474be2ddfca: Pull complete
146f98566145: Pull complete
Digest: sha256:358930e39ff36e0130c3afe3808a5c8f8322f7ff9c42624406dacce859ed0e24
Status: Downloaded newer image for public.ecr.aws/supabase/edge-runtime:v1.67.4
v0.88.9: Pulling from supabase/postgres-meta
1230bc37af91: Pull complete
8a628cdd7ccc: Pull complete
379584f3cbdf: Pull complete
19b45073822c: Pull complete
32fdf0df127c: Pull complete
38bee2b43a68: Pull complete
38eeb4dac3ad: Pull complete
8f5d617dc995: Pull complete
4e462af878e0: Pull complete
b9ff1ff1719c: Pull complete
Digest: sha256:a298c83ab60aa91af9eced2b255f24b0034f487b5393ddc363fa0bca078da0fb
Status: Downloaded newer image for public.ecr.aws/supabase/postgres-meta:v0.88.9
2025.05.05-sha-3c3fe9b: Pulling from supabase/studio
e9fa371f8e95: Pull complete
254e724d7786: Pull complete
3c889a5e6143: Pull complete
bcdabde5c430: Pull complete
e1c750a98ab3: Pull complete
bc4a07156865: Pull complete
fa0e8b42cad0: Pull complete
3abc57c33759: Pull complete
0c4e3d9d5afb: Pull complete
322ae2fb7527: Pull complete
65c80f927f2c: Pull complete
Digest: sha256:9c7e9389ce1e8c540f1484782a21a5af90443c8fa5232e4d1def492ecb4c62e6
Status: Downloaded newer image for public.ecr.aws/supabase/studio:2025.05.05-sha-3c3fe9b
supabase_pg_meta_my-app container logs:
{"level":"info","time":"2025-05-08T00:31:47.461Z","pid":1,"hostname":"ea448def4268","msg":"Server listening at http://0.0.0.0:8080"}
{"level":"info","time":"2025-05-08T00:31:47.506Z","pid":1,"hostname":"ea448def4268","msg":"Server listening at http://0.0.0.0:8081"}
supabase_studio_my-app container logs:
▲ Next.js 15.3.1h checks...
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
▲ Next.js 15.3.1
- Local: http://localhost:3000
- Network: http://0.0.0.0:3000
✓ Starting...
✓ Ready in 3.4s
Stopping containers...
supabase_pg_meta_my-app container is not ready: unhealthy
supabase_studio_my-app container is not ready: starting
Try rerunning the command with --debug to troubleshoot the error.
Sent crash report: a691d3efeaf94e2dba2f5414cfa2ca4c
Quote the crash ID above when filing a bug report: https://github.com/supabase/cli/issues/new/choose
I resolved to using the --ignore-health-check flag, but the container does not run as expected.
> npx supabase start --ignore-health-check
I then downgraded back to Docker Version 4.40.0 (187762)
Started supabase local development setup.
API URL: http://127.0.0.1:54321
GraphQL URL: http://127.0.0.1:54321/graphql/v1
S3 Storage URL: http://127.0.0.1:54321/storage/v1/s3
DB URL: postgresql://postgres:[email protected]:54322/postgres
Studio URL: http://127.0.0.1:54323
Inbucket URL: http://127.0.0.1:54324
JWT secret: super-secret-jwt-token-with-at-least-32-characters-long
anon key: xxx
service_role key: xxxx
S3 Access Key: xxxxxx
S3 Secret Key: xxxxxxxx
S3 Region: local
Thanks to @ThingEngineer (rolling back Docker to version 4.40.0) works
Is this possibly an bug on Docker's end or on Supabase's end? How will we know it's possible to update Docker Desktop again?
Is this possibly an bug on Docker's end or on Supabase's end? How will we know it's possible to update Docker Desktop again?
Version: 4.41.2 (191736) still does not work. I've been watching for the next version and will update if that one works or not.
Seems like a breaking change on the Docker side that needs to be accounted for in Supabase's docker compose, config or the container itself, I have not had the time to dig into it.