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
failed to pull docker image: Error response from daemon: Get "https://public.ecr.aws/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
#2713
Open
edarioq opened this issue
Sep 28, 2024
· 0 comments
Describe the bug
After updating to version 1.200.3 (from 1.191.3) and when running supabase start I get the following error:
failed to pull docker image: Error response from daemon: Get "https://public.ecr.aws/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Retrying after 4s: public.ecr.aws/supabase/postgres:15.6.1.115
failed to pull docker image: Error response from daemon: Get "https://public.ecr.aws/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Retrying after 8s: public.ecr.aws/supabase/postgres:15.6.1.115
Stopping containers...
failed to pull docker image: Error response from daemon: Get "https://public.ecr.aws/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
To Reproduce
Steps to reproduce the behavior:
Go to your project's directory
Run supabase start
Expected behavior
Should pull images and start containers
System information
Rerun the failing command with --create-ticket flag.
Ticket ID: 4023b7d67e0a446cac03d3b9457e0fe8
Version of OS: Sequoia
Version of CLI: 1.200.3
Version of Docker: Docker version 26.1.3, build b72abbb6f0
Additional context
In hindsight this issue could just be caused by macOS Sequoia and some recent firewall update, since disabling the FIrewall fixed the issue for me, if so feel free to close ticket.
The text was updated successfully, but these errors were encountered:
Describe the bug
After updating to version
1.200.3
(from1.191.3
) and when runningsupabase start
I get the following error:To Reproduce
Steps to reproduce the behavior:
supabase start
Expected behavior
Should pull images and start containers
System information
Rerun the failing command with
--create-ticket
flag.supabase/postgres │ 15.6.1.115 │ 15.6.1.115
supabase/gotrue │ v2.160.0 │ v2.160.0
postgrest/postgrest │ v12.2.3 │ v12.2.3
supabase/realtime │ v2.30.34 │ -
supabase/storage-api │ v1.11.7 │ v1.11.7
supabase/edge-runtime │ v1.58.3 │ -
supabase/studio │ 20240729-ce42139 │ -
supabase/postgres-meta │ v0.83.2 │ -
supabase/logflare │ 1.4.0 │ -
supabase/supavisor │ 1.1.56 │ -
Additional context
In hindsight this issue could just be caused by macOS Sequoia and some recent firewall update, since disabling the FIrewall fixed the issue for me, if so feel free to close ticket.
The text was updated successfully, but these errors were encountered: