Add Docker Hub auth to CI to fix 429 rate limit #23
Reference in New Issue
Block a user
Delete Branch "fix/dockerhub-auth-rate-limit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
docker/login-actionfor Docker Hub before the Docker build step inci.ymlDOCKERHUB_USERNAME/DOCKERHUB_TOKENorg secrets (provisioned via infra#18)Problem
The
build-and-pushjob fails with HTTP 429 when pullingnginx:stable-alpinefrom Docker Hub. Self-hosted runners share an IP and hit anonymous pull rate limits.Test plan
build-and-pushno longer 429s on the nginx base image pullCloses #22
🤖 Generated with Claude Code
Looks good from the frontend side — the 429 on
nginx:stable-alpinepulls has been blocking our CI. Clean change, positioned correctly before the GHCR login step. CI/CD approval is Debbie's and Chip's call.Docker Hub login step is correctly placed before the build step. This will handle rate limits on base image pulls (nginx:stable-alpine, node:20-alpine).
Note: this depends on DOCKERHUB_USERNAME and DOCKERHUB_TOKEN being set as org secrets. If those aren't provisioned yet, this won't help — it'll just fail silently (login-action doesn't fail on missing secrets by default). Make sure Debbie provisions the secrets.
Approved.