rpardini/docker-registry-proxy
Some data may be outdated — see provenance labels.
An HTTPS Proxy for Docker providing centralized configuration and caching of any registry (quay.io, DockerHub, registry.k8s.io, ghcr.io) observed · 2026-09-27
Health v2 · maintenance only
75/100
- Activity 82
- Release rhythm 52
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.
- gap_med: 492
- age_days: 3036
- days_rel: 111
- days_push: 111
- n_releases_24m: 2
Adoption not part of the score
1192 stars · 186 forks observed · 2026-09-27
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
An HTTPS caching proxy for Docker registries that provides centralized configuration and caching of image pulls from any registry (DockerHub, quay.io, ghcr.io, registry.k8s.io). It caches large blob/layer downloads to save bandwidth and can cache manifest requests to avoid DockerHub pull rate limits, while centrally managing registry authentication.
Use cases
- cache docker images from dockerhub to avoid rate limits
- set up a pull-through cache proxy for container registries
- reduce bandwidth usage when pulling docker images across a cluster
- centrally manage docker registry credentials for a kubernetes cluster
- mirror quay.io ghcr.io and registry.k8s.io behind one proxy
- avoid toomanyrequests errors when pulling from docker hub
When to choose
- you run kubernetes clusters or CI farms that pull the same images repeatedly and hit DockerHub rate limits
- you want to cache layers/blobs from multiple registries through a single self-hosted proxy
- you need centralized registry authentication instead of configuring imagePullSecrets everywhere
- you want to cut egress bandwidth and pull latency by serving cached layers locally
When to avoid
- you need a full registry with push support - this is a pull-through cache, not a registry you can push to
- you cannot install a CA certificate on the clients that will use the proxy
- you only pull images occasionally from a single machine where rate limits are not a concern
- you need a managed cloud solution rather than running your own proxy container
Facets
service · maturity active
proxy caching security configuration-management self-hosted cloud-computing infrastructure-as-code self-hosted docker-registry-proxy docker-hub pull-through-cache mitm-proxy ca-certificate nginx rate-limit-bypass image-caching kubernetes container-registry containers devops docker linux
1 source
- readme: https://github.com/rpardini/docker-registry-proxy · fetched 2026-09-27 · 0815a1d2b727
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| rpardini/docker-registry-proxy | main | 75 |
For agents
markdown · JSON · MCP: product_card(name="rpardini/docker-registry-proxy")
Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem