Commit ea8b5ea
ci: pull the Supabase base image from Docker Hub
The supabase docker jobs failed twice on "toomanyrequests: Data limit
exceeded" while resolving FROM public.ecr.aws/supabase/postgres. Anonymous
ECR Public pulls are charged to a quota keyed on the source IP, which on
GitHub-hosted runners is a NAT pool shared with every other Actions user.
Supabase publishes the same image to Docker Hub. Both tags resolve to the
same manifest index digest -- 17.6.1.170 to sha256:6087b151...6728f and
15.14.1.170 to sha256:bc165447...70b02 -- with linux/amd64 and linux/arm64
on each, so the published images are unchanged. The docker-publish job
already logs in to Docker Hub before it builds, so these pulls are now
authenticated and counted against our own account.
make postgres-supabase-build is unaffected: its sed already rewrites both
spellings of the FROM line to the running Supabase CLI image tag, which
keeps its public.ecr.aws name so the CLI still picks up the rebuilt image.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>1 parent 1403d3f commit ea8b5ea
2 files changed
Lines changed: 9 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
46 | 46 | | |
47 | 47 | | |
48 | 48 | | |
49 | | - | |
50 | | - | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
51 | 53 | | |
52 | 54 | | |
53 | 55 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
22 | | - | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
23 | 27 | | |
24 | 28 | | |
25 | 29 | | |
| |||
0 commit comments