GHCR vs Docker Hub for CI: Rate Limits, Auth & Speed
Docker Hub rate limits are a top cause of CI flakiness - GHCR changes the trade-offs.
Both store container images; they differ on rate limits, auth, and how tightly they integrate with GitHub Actions.
| Docker Hub | GHCR | |
|---|---|---|
| Rate limits | Strict for anonymous pulls | Tied to GitHub auth |
| Auth in Actions | Manual login | GITHUB_TOKEN built-in |
| Best for | Public base images | Your own images + GitHub workflows |
In CI
Pushing/pulling your own images via GHCR with the built-in GITHUB_TOKEN avoids Docker Hub anonymous rate limits (the classic toomanyrequests failure). For public base images, authenticate to Docker Hub or mirror them.
The verdict
Store your own images in GHCR for seamless Actions auth; authenticate or mirror Docker Hub base images to dodge rate limits.
Related guides
Docker "toomanyrequests: rate limit exceeded" - Fix Docker Hub Pull LimitsFix Docker Hub "toomanyrequests: You have reached your pull rate limit" in CI by authenticating, caching imag…
GHCR vs Amazon ECR: Which Registry for CI?GitHub Container Registry vs Amazon ECR for CI: auth, AWS integration, cost model, and pull speed. Which regi…
GitHub Actions vs CircleCI: Which CI Platform?GitHub Actions vs CircleCI compared: config, orbs vs actions, caching, and integration. Which CI/CD platform…