Closed probablykasper closed 1 year ago
Could you check the CLI version used in your CI workflow? If you are on 1.28.0 and above, the env var SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io
should be automatically set by this action to use the GHCR mirror instead. It has much higher rate limits than ECR when ran from GHA.
- uses: supabase/setup-cli@v1
with:
version: latest
- name: Start Supabase local development setup
run: supabase start
I don't have any version specified, since that's how it's set up in the Supabase CLI docs, so it should be 1.28.3
That seems odd. Could you share with me the expanded action logs to confirm if the env var is set? For eg.
No environment variable there:
Thank you! :DD
Bug report
Describe the bug
I sometimes get this error when running
supabase start
:I'm assuming it's a Docker Hub rate limiting. If there's no way to get around the rate limit, maybe caching could be used to get around it.
To Reproduce
Use the ci.yml from the Supabase "Managing environments" docs, and run it handful of times: