public.ecr.aws/supabase/gotrue:2.142.0 not found: manifest unknown: Requested image not found - wrong version string?

[stefan-girlich]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

(base) ➜  supabase db pull
Connecting to remote database...
Setting up initial schema....
failed to pull docker image: Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.142.0 not found: manifest unknown: Requested image not found
Retrying after 4s: public.ecr.aws/supabase/gotrue:2.142.0

etc.

To Reproduce

1. supabase init
2. supabase link ...
3. supabase db pull => succeeds
4. supabase db pull => fails, see error above

It seems that it should be "v2" instead of "2" here: public.ecr.aws/supabase/gotrue:2.142.0 => public.ecr.aws/supabase/gotrue:v2.142.0

Expected behavior

no error

Screenshots

System information

• OS: macOS

[florentpergoud]

I reproduce on a brand new project with only

npx supabase@latest link
npx supabase@latest start

Giving

Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.142.0 not found: manifest unknown: Requested image not found
Retrying after 4s: public.ecr.aws/supabase/gotrue:2.142.0
Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.142.0 not found: manifest unknown: Requested image not found
Retrying after 8s: public.ecr.aws/supabase/gotrue:2.142.0
Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.142.0 not found: manifest unknown: Requested image not found
Try rerunning the command with --debug to troubleshoot the error.

[Mikodin]

I'm also experiencing this on a brand new project and it's halting me 💔

I don't know if this is the right breadcrumb, but it seems that v is missing
public.ecr.aws/supabase/gotrue:2.142.0

As docker pull supabase/gotrue:v2.142.0 works

https://hub.docker.com/layers/supabase/gotrue/v2.142.0/images/sha256-fc00bd3ff50c4fbd18a1c99c01844d4200eb8a887121065818d665f919f8c474?context=explore

[Mikodin]

@florentpergoud @stefan-girlich
The fix can be found here, in the adjacent issue

supabase/cli#1938 (comment)

[stefan-girlich]

Workaround: echo -n "v2.142.0" > supabase/.temp/gotrue-version

Also see other thread for more info.