i/o timeout #1022
Replies: 4 comments
-
You have a network issue somewhere in your environment. 192.168.65.3 (your Docker machine) tries to do a DNS lookup of registry-1.docker.io on 192.168.65.1 (your apparent DNS resolver) and the request times out. |
Beta Was this translation helpful? Give feedback.
-
My ip address range is 10.0.x.x so was assuming this is on the far end when it is trying to pull the container, but will double check. |
Beta Was this translation helpful? Give feedback.
-
It might be the internal Docker network range. Usually it's a 172.17 address but it can be changed. Not entirely sure how it works on Windows but on Linux it would be the IP subnet assigned to interface docker0. |
Beta Was this translation helpful? Give feedback.
-
For people using Win 10, it appears to be partially related to this issue https://forums.docker.com/t/error-starting-userland-proxy-listen-tcp-0-0-0-0-bind-an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions/81299/5 This allowed postgres to be pulled but stopped with timeout on pulling teslamate. The PC can resolve registry-1.docker.io to 52.5.11.128 Have to investigate further. Have also tried to turning off firewall temporarily but that did not assist. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Doing a fresh install and when running docker-compose up and it tries to pull the latest image and delivers a timeout
PS C:\teslamate> docker-compose up
Pulling teslamate (teslamate/teslamate:latest)...
ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.65.1:53: read udp 192.168.65.3:40463->192.168.65.1:53: i/o timeout
PS C:\teslamate>
Expected behavior
This worked yesterday, but this morning delivers the above error
How to reproduce it (as minimally and precisely as possible):
Relevant entries from the logs
Screenshots
error text copied above
Data
Environment
Beta Was this translation helpful? Give feedback.
All reactions