supabase db remote commit - Error running pg_dump on remote database - No such container

After running

supabase db remote commit

supabase db remote commit

to initialize our initial migration from a current supabase cloud project, we're getting the following error:

Error running pg_dump on remote database - No such container: 8bcf0178bed4199b0de6b37525958b571e2af862e8ff4408208d76eab531a57e

Error running pg_dump on remote database - No such container: 8bcf0178bed4199b0de6b37525958b571e2af862e8ff4408208d76eab531a57e

supabase start

supabase start

does seem to work properly and we have a local environment, we've also linked the remote project already with

supabase link --project-ref $PROJECT_ID

supabase link --project-ref $PROJECT_ID

. Any idea on how to fix this? We want to mature our project into proper CI / CD, Edge Functions.

Supabase•4y ago•

2 replies

After running

supabase db remote commit

supabase db remote commit

to initialize our initial migration from a current supabase cloud project, we're getting the following error:

Error running pg_dump on remote database - No such container: 8bcf0178bed4199b0de6b37525958b571e2af862e8ff4408208d76eab531a57e

Error running pg_dump on remote database - No such container: 8bcf0178bed4199b0de6b37525958b571e2af862e8ff4408208d76eab531a57e

supabase start

supabase start

does seem to work properly and we have a local environment, we've also linked the remote project already with

supabase link --project-ref $PROJECT_ID

supabase link --project-ref $PROJECT_ID

. Any idea on how to fix this? We want to mature our project into proper CI / CD, Edge Functions.