Docker Pulls Keep Timing Out? How to Choose, Configure, and Verify Chinese Registry Mirrors

Wed, 15 Jul 2026 19:30:00 +0800

The short answer When Docker image pulls fail on a mainland China network, the image is not necessarily missing and DNS is not always the culprit. More often, the public registry path is congested, a mirror is temporarily unavailable, or the configuration was edited but Docker was never restarted. My practical recommendation is simple: open status.anye.xyz first and treat it as a “weather report” for Docker mirrors; select a recently healthy HTTPS endpoint; edit the correct daemon configuration for your operating system; validate the JSON; restart Docker; and finally verify with a real pull of a small image.

Docker Images, No More Begging: Build Your Own 13 GB Private Registry From Scratch

Fri, 26 Jun 2026 12:30:00 +0800

TL;DR

My home server runs a single registry:2 container that currently holds 13 GB of cached blobs across 95 repositories. Every NAS, Proxmox node, Mac, and Windows machine on my LAN pulls through it. A cold start of alpine:3.19 finishes in under a second, with zero traffic going out to the public Docker Hub.

This isn’t a one-line “install Docker and run a container” tutorial. I’ll show you the production-grade deployment script I actually run, walk through the Docker v2 auth flow, and call out the four reverse-proxy pitfalls that turn every docker login into a 401 mystery. You’ll leave able to: ① bring up an authenticated registry in 10 minutes; ② explain why the WWW-Authenticate header is sacred; ③ describe the whole thing to a non-technical family member without losing accuracy.

Private Registry on Margrop Blog

Docker Pulls Keep Timing Out? How to Choose, Configure, and Verify Chinese Registry Mirrors

Docker Images, No More Begging: Build Your Own 13 GB Private Registry From Scratch