Unable to pull Docker Images - Windows 10 Fresh installation

Hi, hoping to get some help here.

Updated my Docker installation on Friday to the latest and since then I cannot get any images, they all time out at some point.

Doesn’t matter which source, tried sql, wordpress, etc all end up stuck at waiting on some layers and downloading on others.

Logs as of a few minutes ago:

[09:43:10.221][ApiProxy ][Info ] Dial Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.221][ApiProxy ][Info ] Successfully dialed Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.224][ApiProxy ][Info ] proxy << GET /v1.22/networks/coruspluginswp_default
[09:43:10.228][ApiProxy ][Info ] proxy >> POST /v1.22/networks/create
[09:43:10.228][ApiProxy ][Info ] Dial Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.229][ApiProxy ][Info ] Successfully dialed Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.280][ApiProxy ][Info ] proxy << POST /v1.22/networks/create
[09:43:10.281][ApiProxy ][Info ] proxy >> GET /v1.22/containers/json?all=0&limit=-1&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dcoruspluginswp%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D&trunc_cmd=0&size=0
[09:43:10.282][ApiProxy ][Info ] Dial Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.282][ApiProxy ][Info ] Successfully dialed Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.283][ApiProxy ][Info ] proxy << GET /v1.22/containers/json?all=0&limit=-1&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dcoruspluginswp%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D&trunc_cmd=0&size=0
[09:43:10.313][ApiProxy ][Info ] proxy >> GET /v1.22/containers/json?all=1&limit=-1&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dcoruspluginswp%22%2C+%22com.docker.compose.service%3Ddb%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D&trunc_cmd=0&size=0
[09:43:10.313][ApiProxy ][Info ] Dial Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.313][ApiProxy ][Info ] Successfully dialed Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.314][ApiProxy ][Info ] proxy << GET /v1.22/containers/json?all=1&limit=-1&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dcoruspluginswp%22%2C+%22com.docker.compose.service%3Ddb%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D&trunc_cmd=0&size=0
[09:43:10.316][ApiProxy ][Info ] proxy >> GET /v1.22/containers/json?all=1&limit=-1&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dcoruspluginswp%22%2C+%22com.docker.compose.service%3Dwordpress%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D&trunc_cmd=0&size=0
[09:43:10.316][ApiProxy ][Info ] Dial Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.317][ApiProxy ][Info ] Successfully dialed Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.317][ApiProxy ][Info ] proxy << GET /v1.22/containers/json?all=1&limit=-1&filters=%7B%22label%22%3A+%5B%22com.docker.compose.project%3Dcoruspluginswp%22%2C+%22com.docker.compose.service%3Dwordpress%22%2C+%22com.docker.compose.oneoff%3DFalse%22%5D%7D&trunc_cmd=0&size=0
[09:43:10.319][ApiProxy ][Info ] proxy >> GET /v1.22/images/mysql/json
[09:43:10.319][ApiProxy ][Info ] Dial Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.319][ApiProxy ][Info ] Successfully dialed Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.321][ApiProxy ][Info ] proxy << GET /v1.22/images/mysql/json
[09:43:10.433][ApiProxy ][Info ] proxy >> POST /v1.22/images/create?tag=latest&fromImage=mysql
[09:43:10.439][ApiProxy ][Info ] Dial Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:10.439][ApiProxy ][Info ] Successfully dialed Hyper-V socket 1e1339a9-b2f3-45f5-a914-25468e6a0fec:23a432c2-537a-4291-bcb5-d62504644739
[09:43:17.005][VpnKit ][Info ] Tcp.PCB: ERROR: thread failure; terminating threads and closing connection
[09:43:17.005][VpnKit ][Error ] com.docker.slirp.exe: Lwt.async failure (Invalid_argument
[09:43:17.005][VpnKit ][Info ] “Cstruct.blit src=62906,1260 dst=0,4096 dst-off=3836 len=1260”): Raised at file “format.ml”, line 241, characters 41-52
[09:43:17.005][VpnKit ][Info ] Called from file “format.ml”, line 482, characters 6-24
[09:43:17.005][VpnKit ][Info ]
[09:43:18.914][VpnKit ][Info ] Tcp.Segment: TCP retransmission on timer seq = 452971090
[09:43:20.915][VpnKit ][Info ] Tcp.Segment: TCP retransmission on timer seq = 452971090
[09:43:24.915][VpnKit ][Info ] Tcp.Segment: TCP retransmission on timer seq = 452971090
[09:43:32.915][VpnKit ][Info ] Tcp.Segment: TCP retransmission on timer seq = 452971090
[09:43:48.914][VpnKit ][Info ] Tcp.Segment: TCP retransmission on timer seq = 452971090
[09:44:20.915][VpnKit ][Info ] Tcp.Segment: TCP retransmission on timer seq = 452971090
[09:45:24.914][VpnKit ][Info ] Tcp.Segment: Max retransmits reached for connection - terminating
[09:46:17.178][DnsUpdater ][Info ] Network configuration change detected
[09:46:17.178][PowerShell ][Info ] Run script ‘$(Find-NetRoute -RemoteIPAddress 8.8.8.8).InterfaceIndex[0]’…

I assume that max retransmits is not a good thing, but I am not sure how this issue occurred or what the next best steps are. I am quite new to Docker.

Thanks.

1 Like

Rolled my docker back to Docker for Windows 1.13.1, 2017-02-09 (stable) and the images pulled as expected.

Updated to Docker Community Edition 17.03.0, 2017-03-02 (stable)

Images fail to pull. Luckily I have my images from before but obliviously this work flow is not ideal.

I have several team members effected by this issue as well, including a build server…

@campbech any luck coming to a resolution here? For me I still cannot get new images.

I have not :frowning:. My personal machine seems to be working now, but some of my other machines are still having issues. Are you behind a web proxy by chance? I have only seen this issue while at work.

I am getting this in a work environment.

I created an issue its been acknowledged so fingers crossed!

1 Like

Same here, couldn’t pull images starting from 2 PM UTC+1:

I was able to pull not on my work network. A bit of a pain but a small work around I suppose. It is however not consistent across everyone’s machines here. Seems luck of the draw.

Work around have too started failing… did anyone else make headway?

We have the same problem - image download starts but then stalls partway through. I’ve narrowed it down to our use of a web proxy. If we allow a PC to have direct web access then everything is fine. If it requires a proxy (and DfW is configured to use said proxy) then we get the problem.

Next step is to see if the proxy is the problem (Symantec cloud). The alternative is that it’s the proxy handling code inside the docker engine itself.