Docker Container error when db diff from linked
Hi guys, so for context i have two online instances, one for dev and other for prod. What i normally do is link to dev and db pull and then link to prod to db push. What happened was: i did this flow for a while and a week ago i was having a problem with creating a migration file on dev and i deleted all previous migrations files and and did db pull from my dev which create me a new migration file with all the tables and things i needed. now that im trying to db push to my prod it's saying that i already have a lot of the tables, views, and enums i push from previous migrations. Now i was trying to get the diff from prod vs what i have on my local to be able to push to prod the changes between them. but im having the following error, can someone help me out?
supabase db diff --linked --schema public --file sync_dev_to_prod
Using workdir /Users/alexmorg/Projects/Expo/RoxConnect/rox-connect-app-v2
Creating shadow database...
1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5 container logs:
failed to read docker logs: Error response from daemon: No such container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5
Failed to remove container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5 Error response from daemon: No such container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5
failed to inspect container health: Error response from daemon: No such container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5
Try rerunning the command with --debug to troubleshoot the error.
supabase db diff --linked --schema public --file sync_dev_to_prod
Using workdir /Users/alexmorg/Projects/Expo/RoxConnect/rox-connect-app-v2
Creating shadow database...
1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5 container logs:
failed to read docker logs: Error response from daemon: No such container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5
Failed to remove container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5 Error response from daemon: No such container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5
failed to inspect container health: Error response from daemon: No such container: 1a10aba3570c2d5f82420117d4736dc45312ca5b642d1d09253e6345bfeb65a5
Try rerunning the command with --debug to troubleshoot the error.
