"supabase db dump --local --schema '*' --data-only" fails with cloudfront.net error

[utmostgames]

I've been developing locally on supabase and am ready to export, but my migration files are not available. I'm simply trying to regenerate a schema.sql from local data, but I get this:

$ supabase db dump --local --schema '*' --data-only
Using workdir \source\repos  
Dumping data from local database...  
17.6.1.063: Pulling from supabase/postgres  
failed to display json stream: failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://d5l0dvt14r5h8.cloudfront.net/v2/ec5129...

then it retries:

Retrying after 8s: public.ecr.aws/supabase/postgres:17.6.1.063
17.6.1.063: Pulling from supabase/postgres
32f38e7171bc: Pulling fs layer
be3b7989762c: Pulling fs layer
...
4f4fb700ef54: Already exists
1389d628abeb: Pulling fs layer
a0f5596cb70d: Pulling fs layer
4e577555a793: Pulling fs layer
...

then it does it again (ReadSeeker error and all) and ends with:

c51d86db7691: Pulling fs layer
f3dbb4cb5a79: Download complete
failed to display json stream: failed to copy: httpReadSeeker: failed open: failed to do request: Get "https://d5l0dvt14r5h8.cloudfront.net/v2/c9aad7...

then it stops trying.

It says "Download complete" in the middle there, but there's definitely no file being written.

I want to write a file with my create tables sql; I shouldn't have to go remote to dump a local schema. But here we are.

NOTE: I cannot do 'supabase db push' because the migrations are corrupted; that's why I'm trying to regenerate them.

Help?

• Supabase CLI v.2.72.7

[utmostgames]

Note: Claude decided it would have to run a big mess of these:
docker exec -i supabase_db_repos psql -U postgres -d postgres -c

But I'm sure your team would prefer supabase CLI to work as intended?

[himeshp]

Thanks for the detailed report — based on the logs, the failure is happening while pulling the local Postgres image (public.ecr.aws/supabase/postgres:17.6.1.063) and not during the DB dump itself. The CloudFront URL is part of the image layer download path, so this may be a Docker/registry/network issue (proxy/VPN/DNS), especially on Windows/Docker Desktop.

Could you share:

• OS + architecture
• Docker version (and whether Docker Desktop is using WSL2)
• Whether you’re behind a corporate proxy/VPN

And please try:

1. docker pull public.ecr.aws/supabase/postgres:17.6.1.063
   • If this fails with the same CloudFront error, it confirms the root cause is the image download path rather than supabase db dump.

Also: if your goal is to regenerate schema.sql, --data-only will intentionally exclude schema. If your CLI supports it, try a schema-only dump instead (or remove --data-only) and redirect output to a file (e.g., > schema.sql).

[utmostgames]

@himeshp it was on a Windows box which I've since wiped so I won't be able to recreate. The main issue though is needing a Cloud front endpoint to dump local sql. Not great during early dev. I just wanted to migrate dev to another machine while wiping the windows box.

Keep an eye out, and thanks for the reply