-
Notifications
You must be signed in to change notification settings - Fork 320
Description
Describe the bug
Running supabase db diff results in Error: Address already in use
To Reproduce
Steps to reproduce the behavior:
- run two supabase projects on the same machine
- run
supabase db diff - notice error
Expected behavior
diff works
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with --create-ticket flag.
-
Ticket ID: aedaf6e9470a426fa8aeb85492cd99e0
-
Version of OS: ubuntu 24.04
-
Version of CLI: 2.54.11
-
Version of Docker: 28.5.1
-
Versions of services:
SERVICE IMAGE | LOCAL | LINKED
------------------------|------------------------|--------
supabase/postgres | 17.6.1.029 | -
supabase/gotrue | v2.180.0 | -
postgrest/postgrest | v13.0.7 | -
supabase/realtime | v2.57.3 | -
supabase/storage-api | v1.28.2 | -
supabase/edge-runtime | v1.69.15 | -
supabase/studio | 2025.10.27-sha-85b84e0 | -
supabase/postgres-meta | v0.93.1 | -
supabase/logflare | 1.23.2 | -
supabase/supavisor | 2.7.3 | -
this appears to be related to the open supabase/.temp/profile: no such file or directory occurring and the system falling back to the remote config instead of the local config.toml which defines different shadow ports etc.