supabase start fails with 403 permission error from aws ecr

[KamaniBhavin]

Describe the Bug

Running supabase start fails with the following error:

failed to pull docker image: Error response from daemon: failed to resolve reference "public.ecr.aws/supabase/postgres:15.8.1.054": unexpected status from HEAD request to https://public.ecr.aws/v2/supabase/postgres/manifests/15.8.1.054: 403 Forbidden

---

To Reproduce

Steps to reproduce the issue:

1. Create a new pnpm monorepo
2. Add a new db package
3. Run supabase init inside the package
4. Run supabase start

---

Expected Behavior

The CLI should be able to pull the required Docker images and start a local development environment without errors.

---

Screenshots

N/A

---

System Information

You can rerun the failing command with the --create-ticket flag for more detailed diagnostics.

• Ticket ID: b71ba166f9bf43ca9dacbde70a5c36e0
• OS Version: macOS 15.3.2
• Supabase CLI Version: 2.20.12
• Docker Version: Docker Desktop 4.40.0 (187762)

Service Versions

Service	Local Version	Linked
supabase/postgres	15.8.1.060	-
supabase/gotrue	v2.170.0	-
postgrest/postgrest	v12.2.8	-
supabase/realtime	v2.34.45	-
supabase/storage-api	v1.19.3	-
supabase/edge-runtime	v1.67.4	-
supabase/studio	20250317-6955350	-
supabase/postgres-meta	v0.88.2	-
supabase/logflare	1.12.0	-
supabase/supavisor	2.4.14	-

---

Additional Context

I use private ECR repositories for other projects, each with its own dedicated AWS credential profile. Ideally, this shouldn't interfere with pulling from the public Supabase ECR, but it's possible there's some conflict.

[KamaniBhavin]

It seems that running docker logout public.ecr.aws resolves the issue.