You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Failed to pull docker image - supabase/postgres:15.8.1.018 #2977
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:
Reacted by boutpro, Enrique Enciso, Andrea Tosatto, Christoph and Daniel Bentes
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
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
I get the same issue! when I run supabase start
It was working fine after stopping it and resetting the db I can not start it again!
supabase -v --> 2.15.8
version 27.5.1, build 9f9e405
Error when I run supabase start
failed to pull docker image: Error response from daemon: failed to resolve reference "public.ecr.aws/supabase/postgres:15.8.1.044": failed to do request: Head "https://public.ecr.aws/v2/supabase/postgres/manifests/15.8.1.044": dialing public.ecr.aws:443 container via direct connection because has no HTTPS proxy: connecting to public.ecr.aws:443: dial tcp: lookup public.ecr.aws: no such host
I get the same issue! when I run supabase start It was working fine after stopping it and resetting the db I can not start it again!
supabase -v --> 2.15.8
version 27.5.1, build 9f9e405
Error when I run supabase start
failed to pull docker image: Error response from daemon: failed to resolve reference "public.ecr.aws/supabase/postgres:15.8.1.044": failed to do request: Head "https://public.ecr.aws/v2/supabase/postgres/manifests/15.8.1.044": dialing public.ecr.aws:443 container via direct connection because has no HTTPS proxy: connecting to public.ecr.aws:443: dial tcp: lookup public.ecr.aws: no such host
I could fix it by delete the desktop version of docker and using that insalll it by brew install --cask docker
and in that process it asked me to delete many files that related to old versions and giving permissions
also add run this: nano ~/.docker/daemon.json
and add these config:
Activity
sweatybridge commentedon Dec 17, 2024
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.
jamesfeeder commentedon Dec 17, 2024
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 commentedon Dec 17, 2024
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.018Nciso commentedon Dec 18, 2024
I have the same issue, there is no tag in the registry https://gallery.ecr.aws/supabase/postgres
eluce2 commentedon Dec 18, 2024
Ok, I guess my script was calling
supabase linkwhich was re-creating the version file. If I delete the file and then run thedb pull --linkedcommand, it works for meNextc1 commentedon Dec 19, 2024
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 commentedon Dec 19, 2024
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 commentedon Dec 20, 2024
I forgot to mention that you also need to delete any backup volumes before restarting, ie.
supabase stop --no-backupsweatybridge commentedon Dec 21, 2024
This problem with upstream postgres image has been fixed. supabase/postgres#1372
Ge6ben commentedon Mar 8, 2025
I get the same issue! when I run
supabase startIt was working fine after stopping it and resetting the db I can not start it again!
Error when I run
supabase startGe6ben commentedon Mar 8, 2025
I could fix it by delete the desktop version of docker and using that insalll it by
brew install --cask dockerand in that process it asked me to delete many files that related to old versions and giving permissions
also add run this:
nano ~/.docker/daemon.jsonand add these config:
and also run
sudo chmod 666 ~/.docker/run/docker.sockIn Mac system !