Docker Run can't connect to https://index.docker.io

Docker Desktop for Windows
1

EXPECTED docker run hello-world

Hello from Docker.
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

  1. The Docker client contacted the Docker daemon.
  2. The Docker daemon pulled the “hello-world” image from the Docker Hub.
  3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading.
  4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.

ACTUAL docker run hello-world

C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Network timed out while trying to connect to https://index.dock
er.io/v1/repositories/library/hello-world/images. You may want to check your internet connection or if you are behind a
proxy…
See ‘C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help’.

Information

Client:
Version: 1.11.0
API version: 1.23
Go version: go1.5.4
Git commit: 4dc5990
Built: Wed Apr 13 19:36:04 2016
OS/Arch: windows/amd64

Server:
Version: 1.11.0
API version: 1.23
Go version: go1.5.4
Git commit: a5315b8
Built: Mon Apr 18 08:49:13 2016
OS/Arch: linux/amd64

Steps to reproduce the behavior

docker run hello-world

2 Likes
2

I have exactly the same problem.

3

Same here… I’ll try to install an old version to see if it’s a new bug.

4

Just passing by, it may help somebody. I had this problem myself because I had installed Virtual Box (note I uninstalled it before) before enabling Hyper-V and installing Docker Beta for Windows.

My problem was due to the fact there was still remaining a registry key referring to the old network adapter for the Virtual Box NAT.

I solved it deleting the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxNetAdp and making sure the “vEthernet (DockerNAT)” network adapter IPv4 configuration was set to obtain IP and DNS automatically.

Then I reseted Docker Beta to factory defaults and I run “docker run hello-world” from Git-Bash. It successfully connected to the repository and downloaded the container.

It may be also a good idea to create firewall OUTPUT rules for Docker Proxy and Docker binaries for both TCP and UDP just in case, but there is a good chance they are not needed at all (except of course for the INPUT rules created by default by Docker).

5 Likes
5

  • Fresh Windows 10 version 1511 installation.

  • SIngle ethernet addapter.

  • IPV6 disabled.

  • Firewall disabled.

  • No proxy.

Docker fails from it’s installation.

My log shows this:

[05:37:20.862][Program ][Info ] Version 1.11.1-beta10 (build: 2446)
[05:37:20.905][Program ][Info ] Starting on: 5/5/2016 5:37:20 AM
[05:37:20.908][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources
[05:37:20.911][Program ][Info ] OS: Windows 10 Pro
[05:37:20.913][Program ][Info ] Edition: Professional
[05:37:20.915][Program ][Info ] Id: 1511
[05:37:20.990][Program ][Info ] Build: 10586
[05:37:20.992][Program ][Info ] BuildLabName: 10586.212.amd64fre.th2_release_sec.160328-1908
[05:37:21.025][Program ][Info ] Mixpanel Id: 7C6B4BEE-44FD-4921-B130-46B486B3DC30
[05:37:21.031][Program ][Info ] Sha1: 51937ce6b9f8f70c9a642f493d63db1521a4fb7d
[05:37:21.033][Program ][Info ] You can send feedback, including this log file, at Docker Desktop for Windows - Docker Community Forums
[05:37:22.314][Mixpanel ][Info ] Tracking: appLaunched
[05:37:24.631][Mixpanel ][Info ] Tracking: heartbeat
[05:37:26.813][BackendServer ][Info ] Started
[05:37:27.501][NamedPipeServer][Info ] CheckInstallation:
[05:37:27.504][HyperV ][Info ] Check Hyper-V Windows optional feature
[05:37:27.507][PowerShell ][Info ] Run script…
[05:37:31.788][HyperV ][Info ] Hyper-V Windows feature is enabled
[05:37:31.791][NamedPipeServer][Info ] CheckInstallation done.
[05:37:31.829][NamedPipeServer][Info ] CheckHyperVState:
[05:37:31.833][HyperV ][Info ] Check Hyper-V Service State
[05:37:31.880][PowerShell ][Info ] Run script with parameters: -Check True…
[05:37:43.709][HyperV ][Info ] Hyper-V is running and responding
[05:37:43.715][HyperV ][Info ] Hyper-V is running
[05:37:43.717][NamedPipeServer][Info ] CheckHyperVState done.
[05:37:45.966][Authentication ][Info ] Checking token
[05:37:46.336][Authentication ][Info ] Token is valid
[05:37:46.845][NamedPipeServer][Info ] Start:[2,2048]
[05:37:46.850][Firewall ][Info ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe and C:\Program Files\Docker\Docker\DockerForWindows.exe…
[05:37:46.853][PowerShell ][Info ] Run script…
[05:37:46.888][Updater ][Info ] Checking for updates on the Beta channel…
[05:37:48.488][Updater ][Info ] Found remote version. Version = 1.11.1.2446
[05:37:48.491][Updater ][Info ] Local version is up to date.
[05:37:48.494][Updater ][Info ] Check for update done.
[05:37:52.216][Firewall ][Info ] Ports are opened
[05:37:52.221][HyperV ][Info ] Create
[05:37:52.225][PowerShell ][Info ] Run script with parameters: -Create True -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso…
[05:37:53.411][HyperV ][Info ] Using existing Switch: DockerNAT
[05:37:54.122][HyperV ][Info ] Using existing Switch IP address
[05:37:54.251][HyperV ][Info ] Using existing Net NAT: DockerNAT
[05:37:58.092][HyperV ][Info ] Using existing: MobyLinuxVM
[05:37:58.591][HyperV ][Info ] Setting MobyLinuxVM vm CPUs to 2 and Memory to 2048 MB
[05:37:58.599][Dhcp ][Info ] Dhcp starting on port 67, on interface vEthernet (DockerNAT)…
[05:37:58.647][Dhcp ][Info ] Dhcp started.
[05:37:58.657][Proxy ][Info ] Starting com.docker.proxy
[05:37:58.870][HyperV ][Info ] Start
[05:37:58.874][PowerShell ][Info ] Run script with parameters: -Start True…
[05:37:59.212][Proxy ][Info ] docker proxy (on deprecated port): ready
[05:37:59.227][Proxy ][Info ] dns server: ready
[05:37:59.231][Proxy ][Info ] poison pill: ready
[05:37:59.236][Proxy ][Info ] docker proxy: ready
[05:37:59.839][HyperV ][Info ] Starting VM MobyLinuxVM…
[05:38:02.068][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:03.215][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:04.619][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:05.729][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:08.121][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:09.412][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:10.562][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:11.592][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:12.613][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:13.913][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:15.006][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:16.146][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:17.276][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:18.383][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:19.707][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:20.816][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:22.064][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:23.110][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:24.206][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:25.689][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:26.866][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:26.976][Dhcp ][Info ] DISCOVER received from 00:15:5D:4B:01:09
[05:38:27.005][Dhcp ][Info ] Offer (10.0.75.2) to (00:15:5D:4B:01:09)…
[05:38:27.075][Dhcp ][Info ] Offer sent.
[05:38:27.081][Dhcp ][Info ] DISCOVER processed.
[05:38:27.107][Dhcp ][Info ] REQUEST received from 00:15:5D:4B:01:09
[05:38:27.120][Dhcp ][Info ] Ack (10.0.75.2) to (00:15:5D:4B:01:09)…
[05:38:27.141][Dhcp ][Info ] Ack sent.
[05:38:27.153][Dhcp ][Info ] REQUEST processed.
[05:38:28.148][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:29.178][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:30.201][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:30.796][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 38775 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;docker. IN A
[05:38:30.800][Proxy ][Info ] Search for dns server…
[05:38:31.738][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:32.769][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:33.108][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 38775 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;docker. IN A
[05:38:33.420][Proxy ][Info ] DNS request timed out.
[05:38:33.424][Proxy ][Info ] timeout was 2 seconds.
[05:38:33.428][Proxy ][Info ] Servidor: UnKnown
[05:38:33.432][Proxy ][Info ] Address: 192.168.100.1
[05:38:33.435][Proxy ][Info ]
[05:38:33.438][Proxy ][Info ] Nome: localhost
[05:38:33.443][Proxy ][Info ] Addresses: ::1
[05:38:33.446][Proxy ][Info ] 127.0.0.1
[05:38:33.450][Proxy ][Info ]
[05:38:33.454][Proxy ][Info ]
[05:38:33.493][Proxy ][Info ] Search for dns server…
[05:38:33.500][Proxy ][Info ] Fetch error: Unable to find name server
[05:38:33.906][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:34.923][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:35.588][Proxy ][Info ] DNS request timed out.
[05:38:35.593][Proxy ][Info ] timeout was 2 seconds.
[05:38:35.596][Proxy ][Info ] Servidor: UnKnown
[05:38:35.600][Proxy ][Info ] Address: 192.168.100.1
[05:38:35.603][Proxy ][Info ]
[05:38:35.608][Proxy ][Info ] Nome: localhost
[05:38:35.613][Proxy ][Info ] Addresses: ::1
[05:38:35.617][Proxy ][Info ] 127.0.0.1
[05:38:35.621][Proxy ][Info ]
[05:38:35.625][Proxy ][Info ]
[05:38:35.629][Proxy ][Info ] Fetch error: Unable to find name server
[05:38:35.944][HyperV ][Info ] Wait for the VM to get an IP address
[05:38:37.196][NamedPipeServer][Info ] Start done.
[05:38:37.206][Notifications ][Info ] Docker is running
[05:38:37.209][Mixpanel ][Info ] Tracking: appRunning

No way it’s a VirtualBox trash problem…

I can share my desktop if somebody wants to check it closely.

6

Sorry to hear about that. I only shared my case because it could help people with the same problem as me.

Please check you only have two network adapters enabled, the one you use to connect to the Internet and the vEthernet NAT.

In may case I disabled de Bluetooth network adapter.

7

@ruverav I’ve applied all your suggestion but the issue persists. Here is what I have in my logs (docker pull jenkins)

[13:50:07.045][Proxy ][Info ] proxy >> GET /v1.23/info
[13:50:07.049][Proxy ][Info ] Dial 10.0.75.2:2375
[13:50:07.053][Proxy ][Info ] Dial IP 10.0.75.2:2375
[13:50:07.056][Proxy ][Info ] proxy << GET /v1.23/info
[13:50:07.069][Proxy ][Info ] proxy >> POST /v1.23/images/create?fromImage=jenkins%3Alatest
[13:50:07.073][Proxy ][Info ] Dial 10.0.75.2:2375
[13:50:07.076][Proxy ][Info ] Dial IP 10.0.75.2:2375
[13:50:07.080][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 26484 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;registry-1.docker.io. IN AAAA
[13:50:07.084][Proxy ][Info ] Search for dns server…
[13:50:07.088][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 52788 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;registry-1.docker.io. IN A
[13:50:07.195][Proxy ][Info ] Server: dsldevice.lan
[13:50:07.198][Proxy ][Info ] Address: 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4
[13:50:07.201][Proxy ][Info ]
[13:50:07.204][Proxy ][Info ]
[13:50:07.207][Proxy ][Info ] Found dns server 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4
[13:50:07.210][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:07.213][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:07.216][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:07.219][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:12.071][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 65430 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;registry-1.docker.io. IN A
[13:50:12.076][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:12.079][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:12.082][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 25197 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;registry-1.docker.io. IN AAAA
[13:50:12.085][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:12.089][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:17.071][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 12761 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;index.docker.io. IN AAAA
[13:50:17.076][Proxy ][Info ] Search for dns server…
[13:50:17.079][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 12846 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;index.docker.io. IN A
[13:50:17.199][Proxy ][Info ] Server: dsldevice.lan
[13:50:17.202][Proxy ][Info ] Address: 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4
[13:50:17.205][Proxy ][Info ]
[13:50:17.208][Proxy ][Info ]
[13:50:17.211][Proxy ][Info ] Found dns server 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4
[13:50:17.214][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:17.218][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:17.221][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:17.223][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:22.072][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 63921 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;index.docker.io. IN AAAA
[13:50:22.078][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:22.081][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:22.084][Proxy ][Info ] Handle DNS query ;; opcode: QUERY, status: NOERROR, id: 37462 ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;index.docker.io. IN A
[13:50:22.088][Proxy ][Info ] Forward DNS query on udp to 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:22.092][Proxy ][Info ] Exchange error: dial udp: too many colons in address 2001:8a0:729a:3701:5a98:35ff:fe5a:2bf4:53
[13:50:27.122][Proxy ][Info ] proxy << POST /v1.23/images/create?fromImage=jenkins%3Alatest

I’ve also tried to disable Ipv6 in DockerNat, but it is the same problem.

Any other suggestion?

Thanks

8

Sorry, I don’t have a clue. There’s a lot of people with the same problem, but apparently for different reasons than mine.

Anyways it could be useful to say I have a working Docker Beta on a i7 Surface Pro 4 with an up to day updated Windows 10 Pro. I guess if somebody has the same device than me should know that build 2446 works perfectly for me and it should work for them.

9

I installed version DOCKER VERSION 1.11.1-BETA10 (BUILD: 2446) on a clean computer and it worked! so I removed docker from my computer where i didn’t get it to work, made sure that the internal switch and firewall settings had been removed in the uninstall, then downloaded and installed DOCKER VERSION 1.11.1-BETA10 (BUILD: 2446) and now it works :smiley: happy happy joy joy

10

I will try it again, since my PC still clean…

I’m going to uninstall docker, disable firewall, disable IPV6, remove Hyper-V completely, then try to install is again.

11

Same problem (old virtual box key in registry), same solution! Thanks!

2 Likes
12

I tried again this morning and suddenly it’s working. So, it seems that your solution also worked here. I remember that I was connected to a VPN, which was probably causing some DNS issues.

1 Like
13

Glad to see it’s working for both of you. :+1:

14

Same problem here, on Surface pro 2, without virtual box in registry. Tried uninstall and reinstall without success.

Client:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 5604cbe
Built: Wed Apr 27 00:34:20 2016
OS/Arch: windows/amd64

Server:
Version: 1.11.1
API version: 1.23
Go version: go1.5.4
Git commit: 8b63c77
Built: Fri Apr 29 14:13:26 2016
OS/Arch: linux/amd64

15

Also the same problem and the same solution! Thanks for your hint!

1 Like
16

I had the same problem… I’ve just installed the new release and now it works! :slight_smile:

17

I got it working by setting my DockerNAT connection DNS as 8.8.8.8.

It’s ok now, although I think it should not be a definitive solution…

18

I’ve tried all the tricks mentioned here, but nothing has helped. Seems to be related to some sort of DNS issue.

[15:06:07.536][Proxy ][Info ] Fetch error: Unable to find name server
[15:06:12.191][Proxy ][Info ] proxy << POST /v1.23/images/create?fromImage=hello-word%3Alatest

1 Like
19

The same problem …

I deleted all the Swtich on the Hyper-V.
I also deleted all the Hyper-V ethernet on the Device Manager (I had more than one).
At the end I restarted the machine.

So, I started Docker and it created again the DockerNat Switch and now it works!

20

same problem, no luck so far

this setting (auto ip) crashes docker immediately by me.

v 1.11.1-beta11

i’ve tried everything i could find on this page : i’ve uninstalled vbox and vmware, i have no garbage related to VBoxNetAdp in the registry, i’ve disabled every other network devices, disabled ipv6 and tried 8.8.8.8 as dns for DockerNAT, disabled the firewall, deleted the switch and the server from the hyper-v manager, removed old nat devices from the device manager, rebooted 20 times… have i forgot something ?

i don’t have any other clue yet :worried: