failed to pull docker image: Error response from daemon: failed to resolve reference "public.ecr.aws/supabase/gotrue:v2.184.1": public.ecr.aws/supabase/gotrue:v2.184.1: not found

[timdcochran]

Bug report

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

Describe the bug

A clear and concise description of what the bug is.

supabase db reset/start fails with the following error:

failed to pull docker image: Error response from daemon: failed to resolve reference "public.ecr.aws/supabase/gotrue:v2.184.1": public.ecr.aws/supabase/gotrue:v2.184.1: not found

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

supabase db reset

Expected behavior

Supabase starts

System information

macOS, Supabase installed via brew:

% supabase --version
2.67.1

Additional context

I'm able to manually drop the gotrue version to 2.184.0 as a work around (supabase/.temp/gotrue-version). Version 2.184.1 seems to only be available to Supabase internally.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

⚠️ Possible Duplicate Issue

• https://github.com/supabase/supabase/issues/41770

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[CodersAcademy006]

The CLI appears to pin GoTrue to v2.184.1, but that tag is not available in the public ECR. Rolling the pin back to v2.184.0 (last published tag) fixes supabase start and db reset.

Fix options:

1. Publish gotrue:v2.184.1 to public.ecr.aws, or
2. Roll back the pinned version in the CLI and re-release.