Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Comments

@edarioq
Copy link

edarioq commented Sep 28, 2024

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:

  1. Go to your project's directory
  2. 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
  • Versions of services:
    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant