supabase
Unable to diff or pull against linked project.
I'm setting up a new local development environment for a currently hosted database. I created the local environment, linked to the hosted environment, ran a dump, configured the dump file as the migration file and started the local env. That has all worked well. If I unlink then I can run a local db diff.. However if I link I can't run any diff or pull.. I can still run a dump. I see it spin up a container for a very short time.. Then I get the following error:
supabase db diff -f test
Creating shadow database...
8c585b12130d61a3d25c0a578cfff0769986445fffecefe7c4874b070d572301 container logs:
failed to read docker logs: Error response from daemon: No such container: 8c585b12130d61a3d25c0a578cfff0769986445fffecefe7c4874b070d572301
Failed to remove container: 8c585b12130d61a3d25c0a578cfff0769986445fffecefe7c4874b070d572301 Error response from daemon: No such container: 8c585b12130d61a3d25c0a578cfff0769986445fffecefe7c4874b070d572301
failed to inspect container health: Error response from daemon: No such container: 8c585b12130d61a3d25c0a578cfff0769986445fffecefe7c4874b070d572301
Try rerunning the command with --debug to troubleshoot the error.
I can find the container id in the logs, but I haven't found any info on why it shuts down so quickly.. I get the exact same error when running
supabase db diff -f remote --linked
supabse db pull
If I unlink and run the same command I get the following:
supabase db diff -f test
Creating shadow database...
Initialising schema...
Seeding globals from roles.sql...
Applying migration 20251123174934_initial.sql...
Diffing schemas...
Finished supabase db diff on branch main.
No schema changes found
I've created a ticket:
supabase db diff -f test --create-ticket
Creating shadow database...
0c2935c42e21f2dfde73987ad8234bc56be9d80766970245155c45ece685d2e3 container logs:
failed to read docker logs: Error response from daemon: No such container: 0c2935c42e21f2dfde73987ad8234bc56be9d80766970245155c45ece685d2e3
Failed to remove container: 0c2935c42e21f2dfde73987ad8234bc56be9d80766970245155c45ece685d2e3 Error response from daemon: No such container: 0c2935c42e21f2dfde73987ad8234bc56be9d80766970245155c45ece685d2e3
failed to inspect container health: Error response from daemon: No such container: 0c2935c42e21f2dfde73987ad8234bc56be9d80766970245155c45ece685d2e3
Try rerunning the command with --debug to troubleshoot the error.
Sent crash report: 1ccdaf168e564522972d7b81d8cc8d3f
supabase services
SERVICE IMAGE | LOCAL | LINKED
------------------------|------------------------|-----------
supabase/postgres | 15.1.0.49 | 15.1.0.49
supabase/gotrue | v2.173.0 | v2.173.0
postgrest/postgrest | v10.2.0 | v10.2.0
supabase/realtime | v2.65.3 | -
supabase/storage-api | v1.32.0 | -
supabase/edge-runtime | v1.68.4 | -
supabase/studio | 2025.11.25-sha-8de52c4 | -
supabase/postgres-meta | v0.93.1 | -
supabase/logflare | 1.26.13 | -
supabase/supavisor | 2.7.4 | -
Any suggestions on what may be the cause or how to diagnose a container that doesn't exist? Thanks
No I have not solved it. In my situation I have the local dev set to Postgres 15 because currently that's what my linked project is. When I link and start the local dev it starts Postgres 15.1.0.49 (Yes it's old, I'm trying to test a move to 17) I'm running 2.65.5 CLI.. I have a completely empty local DB, no schemas, no migrations, no link. Run supabase start This starts a Postgres 5.8.1.085 container Run supabase link, supabase stop, supabase start. This starts a Postgres 15.1.0.49 container and all is ok.. Run a supabase db diff -f remote --linked --debug This fails as I originally posted.. Run a supabase stop, supabase start, supabase db diff -f test (still linked) This also fails as originally posted, even tho it's now just a local diff.. supabase unlink, supabase stop, supabase start and the supabase db diff -f test now works, but it's against a Postgres 5.8.1.085 Container.
I have a second project under the same login which when linked to starts Postgres 15.1.0.66 container. That project works correctly..
I've had a hell of time dealing with this. Lots of the issues are solved by deleting the .temp folder which doesn't help when you're trying to diff or pull but these guys seem to have some luck. You can also try this: https://github.com/supabase/supabase/issues/19905
Let me know if any of them help. None of them are actual fixes but they're work arounds
