How to pull Docker images after being blocked

Jul 4, 2024#工具 #docker2208

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

After the domestic Docker source was removed, pulling images in a local network without a proxy became impossible. To set up a CTFD platform that requires images from Docker Hub, a proxy needs to be configured. **Environment:** - Ubuntu host in the local network needs to pull Docker images. - Local IP: 192.168.10.237. **Configuration Steps:** 1. **Modify `daemon.json`:** - Edit the file with `sudo vi /etc/docker/daemon.json` and add: ```json { "registry-mirrors": [ "https://hub.docker.com/" ] } ``` 2. **Create `proxy.conf`:** - Create the directory and file: ```bash mkdir -p /etc/systemd/system/docker.service.d cd /etc/systemd/system/docker.service.d touch proxy.conf ``` - Edit the file with `sudo vi /etc/systemd/system/docker.service.d/proxy.conf` and add: ``` [Service] Environment="HTTP_PROXY=http://192.168.10.237:7890" Environment="HTTPS_PROXY=http://192.168.10.237:7890" ``` 3. **Restart Docker Service:** - Reload the configuration and restart Docker: ```bash systemctl daemon-reload systemctl restart docker ``` 4. **Check Configuration:** - Verify if the proxy settings are applied with: ```bash systemctl show --property=Environment docker ``` **Alternative Temporary Solutions:** - Use a different registry mirror or prepend the image pull command with a specific address: ```bash docker pull docker.1panel.dev/yangchuansheng/derper:latest ``` The goal is to provide stable and secure container image services globally.

After the domestic Docker source was removed, if you want to pull images in a local area network without using a proxy, it really cannot be done. The CTFD platform you built needs to pull images from Docker Hub, so you need to set up a proxy.

Environment:

An Ubuntu host in the local area network needs to pull Docker images, not the local machine
Local machine IP: 192.168.10.237

If the local machine's Docker pulls images, just enable the tun mode in Clash.

Clash proxy settings are as follows:

Modify the daemon.json file:

sudo vi /etc/docker/daemon.json

Add the following content to use the official image:

{
 "registry-mirrors": [
    "https://hub.docker.com/"]
}

Create a proxy.conf file:

mkdir -p /etc/systemd/system/docker.service.d
cd /etc/systemd/system/docker.service.d
touch proxy.conf
sudo vi /etc/systemd/system/docker.service.d/proxy.conf

Add the following content:

[Service]
Environment="HTTP_PROXY=http://192.168.10.237:7890"
Environment="HTTPS_PROXY=http://192.168.10.237:7890"

Restart the Docker service:

# Load the changed configuration
systemctl daemon-reload
# Restart the Docker service
systemctl restart docker

Check if the configuration is effective:

systemctl show --property=Environment docker

Before setting the proxy:

After setting the proxy:

Reference:

https://learnku.com/articles/87396

other#

{  
  "registry-mirrors": [  
        "https://docker.1panel.dev"
    ]  
}

Or add this address as a prefix when pulling images:

docker pull docker.1panel.dev/yangchuansheng/derper:latest

Temporary solution for pulling Docker images that is not a permanent fix

Committed to providing stable, reliable, and secure container image services connecting the whole world

[https://getdocker.quickso.cn/](Docker one-click installation script)