Failed to pull docker image - supabase/postgres:15.8.1.018

[jamesfeeder]

Describe the bug
failed to pull docker image: Error response from daemon: manifest for public.ecr.aws/supabase/postgres:15.8.1.018 not found: manifest unknown: Requested image not found

System information

• Ticket ID: 8af4e9f503d8424faed3b7f20168d3fa
• Version of OS: Fedora Linux 41 (Workstation Edition)
• Version of CLI: 2.0.0
• Version of Docker: 27.4.0
• Versions of services:
  

[sweatybridge]

Hi @jamesfeeder, our postgres team will work out the issue with Postgres image on ECR.

Meanwhile the workaround is to delete the local version file.

rm supabase/.temp/postgres-version

[jamesfeeder]

Thank you 🙏

While I'm using this workaround, Is it able to 'db push' to remote?

Just my curiosity, I don't have any plan to do it right now.

[eluce2]

I'm also having this issue, but deleting that temp file doesn't work for me, it just creates it again with the same version: 15.8.1.018

[Nciso]

I have the same issue, there is no tag in the registry https://gallery.ecr.aws/supabase/postgres

[eluce2]

Ok, I guess my script was calling supabase link which was re-creating the version file. If I delete the file and then run the db pull --linked command, it works for me

[Nextc1]

same issues with different version

failed to pull docker image: Error response from daemon: failed to resolve reference "public.ecr.aws/supabase/postgres:15.8.1.020": public.ecr.aws/supabase/postgres:15.8.1.020: not found

[gaharrington]

Hi @jamesfeeder, our postgres team will work out the issue with Postgres image on ECR.

Meanwhile the workaround is to delete the local version file.

rm supabase/.temp/postgres-version

After I do this, supabase start fails to start:
"supabase/postgres:15.6.1.143 => 15.8.1.020"

Using the --ignore-health-check flag produces the same error.

[sweatybridge]

After I do this, supabase start fails to start

I forgot to mention that you also need to delete any backup volumes before restarting, ie. supabase stop --no-backup

[sweatybridge]

This problem with upstream postgres image has been fixed. supabase/postgres#1372