# anjia0532/gcr.io_mirror

all of the gcr.io docker image mirror

Repository: https://github.com/anjia0532/gcr.io_mirror
Canonical: https://ross.abutalabs.com/products/gcrio_mirror
Language: Go
License: MIT
License Family: permissive
Topics: gcr, k8s, kubernetes, kubectl, docker
Last push: 2024-08-08T00:50:41+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 3215, "days_push": 756, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1390, forks 444 (observed 2026-08-28T04:04:35.582587+00:00)

## What it is
A community-maintained mirror service that re-publishes container images from gcr.io, k8s.gcr.io, registry.k8s.io, quay.io, and ghcr.io to Docker Hub under a predictable naming scheme. Users request image syncs via GitHub issues, which trigger GitHub Actions to pull, retag, and push images automatically.

## Use cases
- pull gcr.io images from China where Google registries are blocked
- mirror k8s.gcr.io images to Docker Hub
- sync a specific quay.io image tag to Docker Hub
- retag registry.k8s.io images for a private registry
- pull ghcr.io images without direct access
- script pulling kubernetes control-plane images via pull-k8s-image.sh

## When to choose
- you cannot reach gcr.io/k8s.gcr.io/registry.k8s.io/quay.io/ghcr.io directly from your network
- you need a one-off image mirrored and don't want to run your own sync pipeline
- you want a forkable GitHub Actions setup to mirror images to your own Docker Hub account

## When to avoid
- you need guaranteed availability or SLAs - the project explicitly disclaims permanence
- you need to verify image integrity - digests differ from upstream after retagging
- you need bulk syncs - only one image per issue is supported
- you require registries beyond the five supported sources without forking and editing rules.yaml
- supply-chain trust matters - malicious upstream images are passed through unmodified

## Facets
- artifact type: service
- maturity: active
- function: container-runtime, deployment, developer-tools
- domain: cloud-computing, self-hosted
- platform: cli
- tags: docker-registry-mirror, gcr.io, k8s.gcr.io, quay.io, ghcr.io, image-sync, github-actions-automation, registry-proxy, containers, devops, docker, kubernetes, github-actions

## Member repositories
- anjia0532/gcr.io_mirror (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:35.582587+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-30T04:39:38.301433+00:00, confidence not recorded.
  - readme: https://github.com/anjia0532/gcr.io_mirror (fetched 2026-08-28T04:04:35.582587+00:00, sha ddf670e2ffc5)
- Data as of 2026-08-30T08:39:29.467469+00:00.