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.02k stars 201 forks source link

CLI fails to pull postgrest v12.1 #2321

Closed ImPrankster closed 3 months ago

ImPrankster commented 4 months ago

Describe the bug When running supabase start the CLI errors with "failed to pull docker image: Error response from daemon: manifest for public.ecr.aws/supabase/postgrest:v12.1 not found: manifest unknown: Requested image not found"

To Reproduce Steps to reproduce the behavior: Run supabase start with an empty project

Expected behavior Does not error

System information Rerun the failing command with --create-ticket flag.

  SERVICE IMAGE │ LOCAL │ LINKED  ─────────────────────────┼──────────────────────┼────────────   supabase/postgres │ 15.1.1.54 │ 15.1.1.54   supabase/gotrue │ v2.151.0 │ v2.151.0   postgrest/postgrest │ v12.1 │ v12.1   supabase/realtime │ v2.28.32 │ -   supabase/storage-api │ v1.2.1 │ v1.2.1   supabase/edge-runtime │ v1.49.0 │ -   supabase/studio │ 20240506-2976cd6 │ -   supabase/postgres-meta │ v0.80.0 │ -   supabase/logflare │ 1.4.0 │ -   bitnami/pgbouncer │ 1.20.1-debian-11-r39 │ -   darthsim/imgproxy │ v3.8.0 │ - 

sweatybridge commented 4 months ago

Could you delete supabase/.temp directory and try again?

I believe this is an issue with PostgREST not released properly on the hosted platform. It affects some linked projects. I've reached out to internal teams to take a closer look.

AaronSmothers commented 4 months ago

Having the same issue here, will try the .temp delete.

AaronSmothers commented 4 months ago

Having the same issue here, will try the .temp delete.

Looks like whatever updates were made has resolved this issue for me. Thanks for the weekend vigilance ya'll.

ImPrankster commented 4 months ago

Having the same issue here, will try the .temp delete.

Looks like whatever updates were made has resolved this issue for me. Thanks for the weekend vigilance ya'll.

I still have the issue, what did u try besides deleting .temp

eifr commented 3 months ago

Could you delete supabase/.temp directory and try again?

I believe this is an issue with PostgREST not released properly on the hosted platform. It affects some linked projects. I've reached out to internal teams to take a closer look.

deleted supabase/.temp fixed it for me :)

sweatybridge commented 3 months ago

We have added PostgREST 12.1 to our ECR and GHCR image registries. This should be fixed now.

williamoverton commented 3 months ago

To fix it for me I had to run supabase link and then delete supabase/.temp