Are you trying to find a solution for the docker error response from daemon i/o timeout? We can help you with it.

Here at Bobcares, we have seen several causes for this error while troubleshooting Docker issues as part of our Docker Hosting Support for Docker users, web hosts, and online service providers.

Today we’ll take a look at the cause for this error and how to fix it.

What causes Docker Error response from daemon I/O timeout to occur

In older versions of dockers, this error occurs due to the DNS issue.

In newer versions of docker, this error occurs due to issue in network infrastructure and is likely the product of latency between the client and the registry.

Here, we need to make sure that there are no proxies in between the client and the registry. Also, the two must be geographically close.

How we fix Docker Error response from daemon I/O timeout

Now let’s see the solution part of this error.

1. DNS Server issue

One of our customers received the below error in the Windows machine.

Error response from daemon: Get https://registry-1.docker.io/v2/library/hello-world/manifests/latest: Get https://auth.docker.io/token?account={your account name here}&scope=repository%3Alibrary%2Fhello-world%3Apull&service=registry.docker.io: dial tcp: lookup auth.docker.io on 192.168.xx.x:5x: read udp 192.168.xx.x:5xxxx->192.168.xx.x:5x: i/o timeout.
See ‘docker run –help’.

Here are the steps our Support Engineers provided to resolve this error.

1. First, right-click on the Docker icon to open Docker Settings.
2. Next, click on the Network tab and change the DNS server from Automatic to Fixed.
3. Finally, click on the Apply button to apply the changes.

Now, the Docker service will restart and must be able to pull the docker images without any issues now.

2. Proxy issue

In another case, the customer was trying to download a docker image using the below command,

sudo docker run hello-world

Since he didn’t have a direct connection and the proxy server was configured in .bashrc file, he was receiving the below error.

Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.xx.xx:53: read udp 192.168.xx.xx:38062->192.168.xx.xx:53: i/o timeout.
See 'docker run --help'.

Below are the steps our Engineers provided to resolve this error.

In the above error, the docker proxy must be configured separately. For that, create a new folder /etc/systemd/system/docker.service.d and create a file http-proxy.conf inside it using the below commands.

mkdir /etc/systemd/system/docker.service.d
cat > /etc/systemd/system/docker.service.d/http-proxy.conf

After that, insert the below proxy information in the file and replace <ip> to your proxy IPs. (make use of vi text editor as well)

[Service]
Environment="HTTP_PROXY=<ip>:808"
Environment="HTTPS_PROXY=<ip>:808"
Environment="NO_PROXY=localhost,127.0.0.1,localaddress,.localdomain.com"

After file configuration, reload docker daemon and restart docker service using the below command.

sudo systemctl daemon-reload
sudo systemctl restart docker

Finally, now the image download must be successful. You can use docker ps -a check the container information.

[Need any further assistance in fixing Docker errors? – We’re available 24*7]

Conclusion

In short, this Docker Error response from daemon I/O timeout mainly occurs due to either DNS error or network infrastructure issue. Today, we saw the solution to this error.