In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-06 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/02 Report--
Cause of event
Yesterday, the developer classmate of the company told me that he always reported an error when pulling the image using docker pull. The error message is as follows:
# docker pull dockerhub.daguan.com/ceshi/data_test:18.12.13.1153Error response from daemon: manifest for dockerhub.daguan.com/ceshi/data_test:18.12.13.1153 not found
I began to pull the mirror image test on my Mac book and found that it can be pulled normally!
Reason for reporting an error
After trying to check the messages information of the system, it is found that it is a network problem, as follows:
Dec 20 11:13:46 dockertest dockerd: time= "2018-12-20T11:13:46.498227008+08:00" level=error msg= "failed removing service binding for xxxxxx epRec: {rec_priv_indexing.1.xxxx rec_priv_indexing xxxxxx 192.168.246.171 192.168.246.250 [] [indexing] [xxxxxx]} err:network xxxxxxxx not found"
Description: the above irrelevant information has been ignored by xxxx ~
Later, I remembered that the company's dockerhub library platform had been migrated before, and the domain name resolution IP had been changed!
Processing error report
Try to modify / etc/hosts to force docker.io-related domain names to be resolved to other available IP.
Vim / etc/hosts
Add an available IP:
110.200.19.34 dockerhub.daguan.com / / Please change to your own IP and domain name
Try again after saving and have returned to normal!
Extended learning
If the following "timeout" error message appears, you can also try the above repair method, as follows:
Error response from daemon: Get https://index.docker.io/v1/users/: dial tcp: lookup index.docker.io on 192.168.65.1 lookup index.docker.io on 53: read udp 192.168.65.2 dial tcp 58812-> 192.168.65.1 dial tcp 53: I timeout
Or:
If you use the above method to modify / etc/hosts, which has no effect, please change the Docker subnet IP address range on your computer, as follows:
In the figure above, we see that there is a problem with the 192.168.65.1 network segment, so we can change the Docker subnet to 192.168.66.0 and restart docker!
Or:
[root@archlinux quanxj] # docker image pull library/hello-world Using default tag: latest latest: Pulling from library/hello-world ca4f61b1923c: Pull complete error pulling image configuration: Get https://registry-1.docker.io/v2/library/hello-world/blobs/sha256:f2a91732366c0332ccd7afd2a5c4ff2b9af81f549370f7a19acd460f87686bc7: dial tcp 35.169.231.249 docker image pull library/hello-world Using default tag 443: iActiono timeout reference documentation
Solve Error response from daemon: Get https://registry-1.docker.io/v2/library/hello-world/manifests/
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.