Cloud Native 4 min read

Boost Docker Pull Speed with Chinese Mirror Accelerators: Step-by-Step Guide

This article explains how to configure Docker and Containerd to use domestic image‑mirror services, providing detailed commands and verification steps that dramatically reduce image‑pull latency and improve development and operations efficiency in cloud‑native environments.

Linux Ops Smart Journey
Linux Ops Smart Journey
Linux Ops Smart Journey
Boost Docker Pull Speed with Chinese Mirror Accelerators: Step-by-Step Guide

In the cloud‑native era, container technologies like Docker and Containerd are standard for building, deploying, and running applications. Pulling images from public registries such as Docker Hub can be slow, especially under poor network conditions or remote locations.

Container diagram
Container diagram

Image Acceleration Services

Domestic mirror services can be configured to speed up pulls. Examples include:

https://dockerhub.icu

https://docker.hlyun.org

Configuration Steps

1. Add an insecure registry parameter to Docker's config file:

"registry-mirrors": [
    "https://dockerhub.icu"
],

2. Apply the configuration:

$ sudo kill -1 $(ps -ef | grep [d]ockerd | awk '{print $2}')

3. Verify the effective configuration:

$ sudo docker info | awk '/Mirrors/,/Live/ {print $0}' | grep http
https://dockerhub.icu/

Image Pull Verification

1. Capture packets while pulling an image:

$ tcpdump -i ens33 -enn '(udp and port 53) or (host dockerhub.icu)' -w dockerhub.pcap

Tip: The command only captures DNS packets and those destined for dockerhub.icu.

2. Pull an image from hub.docker.com:

$ docker pull docker.io/library/debian:stable-slim
stable-slim: Pulling from library/debian
Digest: sha256:...
Status: Image is up to date for debian:stable-slim

3. Inspect the captured packets. If the traffic is only with the public IP resolved from dockerhub.icu, the mirror configuration succeeded.

Packet capture example
Packet capture example

Conclusion

Following these steps can dramatically improve Docker image pull speed, saving time and enhancing development and operations efficiency. Selecting a stable, fast mirror is essential for a smooth container workflow.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Cloud NativeDockerperformance optimizationLinuxImage Mirror
Linux Ops Smart Journey
Written by

Linux Ops Smart Journey

The operations journey never stops—pursuing excellence endlessly.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.