Docker related issues
The two most common problems with pulling Docker images, and their fixes.
The server cannot pull images
Section titled “The server cannot pull images”On some servers, especially in Russia, Docker Hub is unreachable and images do not download (see issue #40). The fix is registry mirrors.
-
Create or open the
daemon.jsonfile:root@server: ~ nano /etc/docker/daemon.json -
Paste the mirror configuration:
daemon.json {"log-driver": "local","registry-mirrors": ["https://mirror.gcr.io/","https://dockerhub.timeweb.cloud"]} -
Restart the Docker service:
root@server: ~ systemctl restart docker -
Check that the mirrors were picked up:
root@server: ~ docker info | grep -A 3 "Registry Mirrors"
You have reached your unauthenticated pull rate limit
Section titled “You have reached your unauthenticated pull rate limit”This message means the download limit for anonymous requests to Docker Hub is exhausted. What you can do:
-
Log in to Docker Hub:
root@server: ~ docker loginAuthenticated requests are counted per account, not per server address.
-
Change the server’s external address
The limit is tied to the IP: if the address is dynamic, restarting the server helps; otherwise ask your hoster about changing the address.
-
Enable IPv6
Run
remnawave_reverse, select item10(Manage IPv6), and enable IPv6 support. Downloads then go from a different address, and the limit often lets go.
My problem is not listed here
Section titled “My problem is not listed here”Feel free to report any issues related to our project in the GitHub repository or the Telegram chat.
