# rpardini/docker-registry-proxy

An HTTPS Proxy for Docker providing centralized configuration and caching of any registry (quay.io, DockerHub, registry.k8s.io, ghcr.io)

Repository: https://github.com/rpardini/docker-registry-proxy
Canonical: https://ross.abutalabs.com/products/docker-registry-proxy
Language: Shell
License: Apache-2.0
License Family: permissive
Topics: docker, docker-registry, docker-mirror, kubernetes, https-proxy, ca-certificate
Last push: 2026-07-01T11:20:47+00:00

## Health v2 (maintenance only)
Score: 81/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 90, release rhythm 59, longevity 100
- inputs: {"age_days": 2988, "days_push": 63, "days_rel": 63, "gap_med": 492, "n_releases_24m": 2}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1186, forks 185 (observed 2026-08-28T04:03:55.067172+00:00)

## What it is
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
- artifact type: service
- maturity: active
- function: proxy, caching, security, configuration-management
- domain: self-hosted, cloud-computing, infrastructure-as-code
- platform: self-hosted
- tags: 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

## Member repositories
- rpardini/docker-registry-proxy (main) score 81

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:55.067172+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:24:04.291584+00:00, confidence not recorded.
  - readme: https://github.com/rpardini/docker-registry-proxy (fetched 2026-08-28T04:03:55.067172+00:00, sha 0815a1d2b727)
- Data as of 2026-08-30T08:39:29.467469+00:00.