# Self-Healing CI: Auto-Retrying Docker Hub Pull Rate Limits (429)

> Docker Hub pull-rate limits (429 Too Many Requests) are transient and shared. See the manual fix and how self-healing CI retries the pull automatically.

Source: https://latchkey.dev/learn/self-healing-ci/self-heal-dockerhub-rate-limit-429  
Updated: 2026-06-25

A Docker Hub 429 is not a build problem - it is a quota that resets. The same pull usually succeeds a short time later, or once the request is authenticated.

## What makes a failure safely retryable

Automatic retry is only correct for failures that are genuinely transient. Retrying a deterministic failure wastes minutes and hides a real defect, so the classification matters more than the retry mechanism.

- Safe to retry: network timeouts, registry 5xx, transient DNS failures, a service container that was not ready, a spot instance reclaimed mid-run.
- Not safe to retry: assertion failures, compile errors, lint violations, anything that fails identically on every attempt.
- Ambiguous, and worth investigating rather than retrying: out-of-memory kills, disk exhaustion, and flaky tests. These repeat under load and a retry only hides the trend.
- Always record that a retry happened. A pipeline that silently retries is a pipeline whose real failure rate you do not know.

## FAQ

### Why do I hit a Docker Hub rate limit when I barely pull any images?

Because the limit is per source IP, and hosted CI shares egress IPs across many customers. Your job inherits a quota that other tenants on the same IP may have already spent - which is exactly why an automatic backoff-and-retry, or an authenticated/cached pull, clears it.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt