Chinaready Docker Hub Mirror is now generally available — a Docker Hub China pull-through cache at docker-hub.chinaready.co for public images when registry-1.docker.io is blocked or rate-limited from Mainland China. The educational path — mirrors, private registries, digest pins — stays on Docker Hub in China.
When docker pull fails from Mainland China
CI and laptops that still docker pull official or public Hub images on Mainland China networks fail often enough to stall a release. Hub is slow or unreachable often enough that “it worked this morning” is still a pipeline defect. Authentication can ease overseas rate limits; it does not make Docker Hub a dependable China source.
That is a registry host problem, not a yes/no “does Docker work” SKU. Keep-build-overseas, vendor mirror, and in-country Harbor forks live in the Guide. This post is the named Chinaready cache for public Hub pulls.
A working pull through this mirror does not, by itself, make a cluster ready for Mainland China. Private images, Helm defaults, runtime Hub pulls on scale-out, and where the workload runs still need a registry strategy.
What general availability includes
The service is a read-only pull-through cache, not a private registry you push to, and not a catalog you write. Public Docker Hub images are fetched from Hub once, then served from the Singapore origin through the Mainland China–reachable endpoint.
Included
- Public-image Pull for approved and allowlisted users
- A shared public trial account that may pull
library/alpine,library/nginx, andlibrary/ubuntu - Allowlisted users who sign in with their Docker Hub username and a personal access token, then pull any public Hub repository through the mirror
- Identity check against Docker Hub only — the token is not stored and is not used for upstream image pulls
Not included
- Push, delete, or catalog writes
- Private repositories
- A replacement for an in-country Harbor / ACR / TCR / CCR you control
- Digest policy, Helm overrides, or cold-pull proof on China runners — those stay in Docker Hub in China
The utility sits beside Google Fonts for China and Frontend CDN as free China-launch infrastructure. It is not a paid service SKU.
How to try a Docker Hub China pull
Start with the public trial account public/chinareadyco. After a successful login, pull one of the three public trial images:
docker login docker-hub.chinaready.co
docker pull docker-hub.chinaready.co/library/alpine:latestA successful pull means the Docker Hub mirror works on that network. Other repositories need allowlisted access. To apply, use Contact Us with your Docker Hub username and intended use. The service is free for Chinaready contracted customers.
Allowlisted login uses your Docker Hub username and personal access token. Only public-image Pull is supported.
Who this is for
Teams whose Mainland China runners, laptops, or staging nodes still hit registry-1.docker.io for public bases — alpine, nginx, ubuntu, and the rest of the public Hub graph — and who need a named, authenticated pull-through cache instead of an informal mirror list.
If the job is production Kubernetes that must never depend on Hub, keep the Guide’s overseas-build-then-sync or in-country private registry patterns. This cache is a vendor pull-through for public images, not the whole China registry policy.
A free utility, not a full registry verdict
Chinaready Docker Hub Mirror is operated by Chinaready as a Docker Hub China pull-through cache so public images can take a path that works from Mainland China when Hub is blocked or rate-limited.
It does not replace digest pins, private registries, or the CI redesign on Docker Hub in China. If Hub is only one of several uncertain dependencies, the China Readiness Assessment maps the stack.
Open Docker Hub Mirror to try the public trial pull, then request allowlisted access when you need more than alpine, nginx, and ubuntu.
