search

supabase / cli

Supabase CLI. Manage postgres migrations, run Supabase locally, deploy edge functions. Postgres backups. Generating types from your database schema.
https://supabase.com/docs/reference/cli/about
MIT License
1.07k stars 209 forks source link

supabase start CLI command failing to pull from AWS ECR #2645

Closed thomaswilsonxyz closed 2 months ago

thomaswilsonxyz commented 2 months ago

Describe the bug

When attempting to run supabase start, the CLI reports a failure response from AWS's ECR (Error response from daemon: Get "https://public.ecr.aws/v2/")

This error prevents a local supabase instance from starting.

To Reproduce

  1. Have a pre-existing, linked Supabase project
  2. if there's a local supabase instance running, supabase stop it
  3. run supabase start

additionally i can reproduce an identical error by attempting to docker pull public.ecr.aws/supabase/storage-api:v1.6.8

Expected behavior I'd expect to see a Docker Container with the Supabase Services start

Screenshots (didn't want to attach a screenshot of nothing happening)

System information

       SERVICE IMAGE      │      LOCAL       │  LINKED
  ─────────────────────────┼──────────────────┼────────────
    supabase/postgres      │ 15.1.1.78        │ 15.1.1.78
    supabase/gotrue        │ v2.158.1         │ v2.158.1
    postgrest/postgrest    │ v12.2.2          │ v12.2.2
    supabase/realtime      │ v2.30.23         │ -
    supabase/storage-api   │ v1.10.3          │ v1.10.3
    supabase/edge-runtime  │ v1.56.1          │ -
    supabase/studio        │ 20240729-ce42139 │ -
    supabase/postgres-meta │ v0.83.2          │ -
    supabase/logflare      │ 1.4.0            │ -
    supabase/supavisor     │ 1.1.56           │ -

Additional context

when running with --debug flag, the tail end of the logs gives us:

2024/08/30 07:21:55 Recv First Byte
2024/08/30 07:21:56 Sent Header: Host [api.moby.localhost]
2024/08/30 07:21:56 Sent Header: User-Agent [Docker-Client/unknown-version (darwin)]
2024/08/30 07:21:56 Sent Header: Content-Length [0]
2024/08/30 07:21:56 Sent Header: X-Registry-Auth [e30=]
2024/08/30 07:21:56 Send Done
2024/08/30 07:22:00 Recv First Byte
failed to pull docker image: Error response from daemon: Get "https://public.ecr.aws/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: connection timed out
Retrying after 4s: public.ecr.aws/supabase/realtime:v2.30.23
2024/08/30 07:22:04 Sent Header: Host [api.moby.localhost]
2024/08/30 07:22:04 Sent Header: User-Agent [Docker-Client/unknown-version (darwin)]
2024/08/30 07:22:04 Sent Header: Content-Length [0]
2024/08/30 07:22:04 Sent Header: X-Registry-Auth [e30=]
2024/08/30 07:22:04 Send Done
2024/08/30 07:22:09 Recv First Byte
failed to pull docker image: Error response from daemon: Get "https://public.ecr.aws/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: no route to host
Retrying after 8s: public.ecr.aws/supabase/realtime:v2.30.23
2024/08/30 07:22:17 Sent Header: Host [api.moby.localhost]
2024/08/30 07:22:17 Sent Header: User-Agent [Docker-Client/unknown-version (darwin)]
2024/08/30 07:22:17 Sent Header: Content-Length [0]
2024/08/30 07:22:17 Sent Header: X-Registry-Auth [e30=]
2024/08/30 07:22:17 Send Done
2024/08/30 07:22:21 Recv First Byte
Stopping containers...
Pruned containers: [27c99dcbeae676d542583631dc0048b3fd91e1e6e220d81e3b59e40085aa1aea 39af3872bf599695db12678a0e96be74e87d735dbf72ecb21068f263224412e6 90fad87f3964d60b3b6e82565a088aea5ac2131eed6a15a707abeef6566172fa 260f65b51753783a45f8eb6e27083963defcaaef7d4c4885be8de916226a689d]
Pruned network: [supabase_network_hono-api]
failed to pull docker image: Error response from daemon: Get "https://public.ecr.aws/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: no route to hos
sweatybridge commented 2 months ago

Does this suggestion work for you? https://github.com/supabase/cli/issues/2210#issuecomment-2076704407

thomaswilsonxyz commented 2 months ago

hi, @sweatybridge !

it does not 😞 

failed to pull docker image: Error response from daemon: Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: connection timed out
Retrying after 4s: supabase/postgres:15.1.1.78
failed to pull docker image: Error response from daemon: Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: connection timed out
Retrying after 8s: supabase/postgres:15.1.1.78
Stopping containers...
failed to pull docker image: Error response from daemon: Get "https://registry-1.docker.io/v2/": proxyconnect tcp: dial tcp 192.168.65.1:3128: connect: connection timed out
Try rerunning the command with --debug to troubleshoot the error.
thomaswilsonxyz commented 2 months ago

okay, this has resolved itself after two reboots (which i suspect is a bit of a rain-dance, not an actual solution).

. i think possibly:

thanks for your time/attention, @sweatybridge !

i am happy to mark this as resolved.

thomaswilsonxyz commented 2 months ago

resolved (see above)

sweatybridge commented 2 months ago

Happy to hear that you managed to resolved it!