Chinaready utility

Chinaready Docker Hub Mirror.

A production read-only pull-through cache for approved users in mainland China. Public Docker Hub images are served from Singapore after the first fetch from Hub — a reliable path when registry-1.docker.io is blocked or rate-limited.

RO

Read-only
No push or catalog write

3

Public repos
alpine · nginx · ubuntu

SG

Singapore origin
Pull-through cache

CN

Mainland China
Reachable endpoint

Usage

How to use Chinaready Docker Hub Mirror

Start with the public trial account public/chinareadyco. After a successful login, try pulling the three public trial images.

Access URLs are unchanged

The registry endpoint docker-hub.chinaready.co is unchanged — docker login and docker pull keep using the full host exactly as before. This page only consolidates the documentation on launchready.cn.

Sign in

docker login docker-hub.chinaready.co

Pull an image

docker pull docker-hub.chinaready.co/library/alpine:latest

A successful pull means this mirror works on your network. The service is free for Chinaready contracted customers — contact Chinaready if you need access.

Access

Apply to use this service

Sign in with your Docker Hub username and personal access token. Only public-image Pull is supported — other operations are not available.

Public account

The shared public account may pull three repositories only:

  • library/alpine
  • library/nginx
  • library/ubuntu

All other repositories need allowlisted access.

Allowlisted access

Allowlisted users authenticate with their Docker Hub username and a personal access token. The token verifies identity against Docker Hub only — it is never stored and is not used for upstream image pulls.

After verification you may pull any public Docker Hub repository through this mirror.

FAQ

Chinaready Docker Hub Mirror FAQ

Why does this service exist?
Docker Hub is blocked or rate-limited from mainland China. This mirror caches public images in Singapore after the first Hub fetch for approved users.
Why do pulls from mainland China look stuck?
The origin is in Singapore. Client paths from mainland China (and some nearby networks) often deliver only tens of KB/s. Small layers can appear stuck for a long time with little visible progress, but they usually complete. That is path latency and bandwidth — not a mirror outage. Auth and manifests succeed; multi-MB blobs keep transferring slowly until finished.
What can the public account pull?
Only library/alpine, library/nginx, and library/ubuntu.
How do allowlisted users authenticate?
Docker Hub username plus a personal access token. The token is checked against Hub identity services and discarded — never stored on the mirror.
Can I push images?
No. The mirror is pull-through and read-only. Push, delete, and catalog writes are blocked.
How does this relate to Chinaready?
It is a Chinaready infrastructure utility for China-facing container workflows — complementary to services such as Chinaready Google Fonts. For background, see Docker Hub in China.

Need allowlisted pull access?

Tell us your Docker Hub username and intended use. We review requests and add approved accounts to the allowlist.