Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to solve i/o timeout error in docker pull

When trying the command:

docker pull alpine

I am getting the following error

error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/e2/e21c333399e0aeedfd70e8827c9fba3f8e9b170ef8a48a29945eb7702bf6aa5f/data?Expires=1514733515&Signature=VxGVBTpdVnoFQYVSYjf-xOAYENczOPcAp7BZsxEZI6EyoiRgvKsOmxFkb7MgCMau~yVa59uHJcdq5KmCWKD6G3Cnsr2V2CdXrEIZ~P-Kt-74m8LKsjbTzw2yw~ABuLOs5c7OI9-2LFB5XOrFjgBaDUKPGDpyWsLMLz7QAh-vNrM_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp 218.248.255.164:443: i/o timeout

The docker --version is 17.09.1-ce, build 19e2cf6. The docker-compose --version is 1.17.1, build 6d101fb. Trying these commands from OSX El Capitan.

It was suggested somewhere that changing the DNS server to public DNS would solve this that didn't work, either.

like image 654
das Avatar asked Dec 31 '17 11:12

das


People also ask

How do I stop docker pull limits?

All you have to do to avoid Docker's new rate-limit error is authenticate to your Docker Hub account. After you've authenticated to the account, you won't be pulling the image as an anonymous user but as an authenticated user.

How do I fix x509 certificate signed by unknown authority docker?

How to resolve Docker x509: certificate signed by unknown authority error. In order to resolve this error, we have to import the CA certificate in use by the ICP into the system keystore. Then, we have to restart the Docker client for the changes to take effect.

What is docker pull limit?

Pull rates limits are based on individual IP address. For anonymous users, the rate limit is set to 100 pulls per 6 hours per IP address. For authenticated users, it is 200 pulls per 6 hour period. Users with a paid Docker subscription get up to 5000 pulls per day.


1 Answers

As discussed in the comments, you tried to ping the host dseasb33srnrn.cloudfront.net and it is not responding (it responds to my ping), which means the problem is in your system DNS settings, and not in Docker:

Please check the DNS settings in /etc/resolv.conf, if you do not sure what to do, just paste this text inside that file (and remove any other nameservers):

nameserver 8.8.8.8
nameserver 8.8.4.4

This should work, although it is not the optimal way, I will edit my answer to add the most elegant way when you try it.

like image 167
Mohammed Noureldin Avatar answered Sep 28 '22 09:09

Mohammed Noureldin