cli: failed to pull docker image
Describe the bug
When I run supabase start I get this error:
failed to pull docker image: Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.139.2-rc.7
not found: manifest unknown: Requested image not found
To Reproduce Install the latest version of supabase:
"supabase": "^1.142.2",
Expected behavior No errors
System information
Rerun the failing command with --create-ticket flag (preferred).
- Ticket ID: cf89590c829d4353bb8226495c762c88
- OS: Windows 11
- Version of CLI: 1.142.2
- Versions of services:
SERVICE IMAGE │ LOCAL │ LINKED
─────────────────────────┼──────────────────────┼───────────────
supabase/postgres │ 15.1.0.137 │ 15.1.0.137
supabase/gotrue │ 2.139.2-rc.7 │ 2.139.2-rc.7
postgrest/postgrest │ v11.2.2 │ v11.2.2
supabase/realtime │ v2.25.50 │ -
supabase/storage-api │ v0.46.5 │ v0.46.5
supabase/edge-runtime │ v1.33.5 │ -
supabase/studio │ 20240101-8e4a094 │ -
supabase/postgres-meta │ v0.75.0 │ -
supabase/logflare │ 1.4.0 │ -
bitnami/pgbouncer │ 1.20.1-debian-11-r39 │ -
darthsim/imgproxy │ v3.8.0 │ -
J
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 4
- Comments: 17 (3 by maintainers)
I could not get any of the older versions or fixed mentioned above to work unfortunately, as this issue just started happening for me today. Deleting the
supabase/.temp/gotrue-versionfile worked for meTurns out the
vprefix was accidentally dropped from gotrue’s/healthendpoint response but the docker image was still tagged asv2.142.0. There’s an upstream PR to fix it. Once it’s rolled out, running link and start should work again.So I temporarily fixed it by removing the version in
supabase/.temp/gotrue-version, however, it still wants to link to a non-existent version:Should the cloud version be using a version that is not downloadable? This breaks the link.
J
It looks like we don’t have version 2.139.2-rc.7 published on docker hub. I will ping our auth team to take a look. Sorry for the inconvenience.
No because then it will ask me to relink. That is not the version installed on the cloud. Also, that is
supabase cliyou’re talking about, notgotrue. If I change the version, I get:@gillesmag - Run
npx supabase link(which will update your gotrue version), thennpx supabase startand I bet yours isn’t fixed.J
I just ran into the same issue, pulling the image with the
vtag prefix and tagging the image with the expected image name fixed it for me.@sweatybridge Sorry - I accidentally deleted my previous content; restoring it below:
I am getting a new error after hotfixng
supabase/.temp/gotrue-versionto include the “v” character:@sweatybridge It seems there are no newline characters in the file. I will check if vim left any kind of control characters.
Update: This did the trick:
echo -n "v2.142.0" > supabase/.temp/gotrue-versionWe’re in the same boat over here https://github.com/supabase/supabase/issues/21300
This worked, all I had to do was add a
vin front of the version number insupabase/.temp/gotrue-version