Docker Community Forums

Share and learn in the Docker community.

Pulling Large images fails

docker

(Nicolas Bihan) #1

Expected behavior

Being able to pull images

Actual behavior

When downloading big images from a local registry (Artifactory 4.11) the pull stops randomly, sometimes shortly after I started the pull, sometimes after few minutes (image is 8.5GB).
I am able to pull smaller images from Artifactory. I am able to pull the same images from the same registry on a Ubuntu VM on the same machine.

Information

host distribution and version (Windows version, build number, etc)
Docker for Windows, Docker version 1.12.0, build 8eab29e, experimental
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:04:48 2016
OS/Arch: windows/amd64
Experimental: true

Server:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 21:04:48 2016
OS/Arch: linux/amd64

Steps to reproduce the behavior

docker pull imagename

wait for it to hung

Here is the logs I have on my local docker

[15:29:56.917][VpnKit ][Debug ] com.docker.slirp.exe: Socket.Datagram.input 192.168.65.2:37267-10.0.75.1:53 (DNS[89cc]): shutting down listening thread
[15:30:03.672][VpnKit ][Debug ] com.docker.slirp.exe: ARP responding to: who-has 192.168.65.1?
[15:30:13.251][VpnKit ][Info ] Restarting…
[15:30:13.457][PowerShell ][Info ] Run script…
[15:30:13.513][VpnKit ][Info ] Restarted
[15:30:13.534][VpnKit ][Info ] com.docker.slirp.exe: Logging to stdout (stdout:true DEBUG:false)
[15:30:13.539][VpnKit ][Info ] com.docker.slirp.exe: Setting handler to ignore all SIGPIPE signals
[15:30:13.542][VpnKit ][Info ] com.docker.slirp.exe: vpnkit version %VERSION% with hostnet version local %HOSTNET_PINNED% uwt version 0.0.3 hvsock version 0.10.0 %HVSOCK_PINNED%
[15:30:13.546][VpnKit ][Info ] com.docker.slirp.exe: starting port_forwarding port_control_url:hyperv-connect://f0949704-c9e2-4af9-b2f8-f28d7a8efeef max_connections:None vsock_path:
[15:30:13.549][VpnKit ][Info ] com.docker.slirp.exe: connecting to f0949704-c9e2-4af9-b2f8-f28d7a8efeef:0B95756A-9985-48AD-9470-78E060895BE7
[15:30:13.553][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://f0949704-c9e2-4af9-b2f8-f28d7a8efeef
[15:30:13.557][VpnKit ][Warning] com.docker.slirp.exe: no database: using hardcoded network configuration values
[15:30:13.560][VpnKit ][Info ] com.docker.slirp.exe: connecting to f0949704-c9e2-4af9-b2f8-f28d7a8efeef:30D48B34-7D27-4B0B-AAAF-BBBED334DD59
[15:30:13.564][VpnKit ][Debug ] com.docker.slirp.exe: Waiting for connections on socket hyperv-connect://f0949704-c9e2-4af9-b2f8-f28d7a8efeef
[15:30:13.567][VpnKit ][Info ] com.docker.slirp.exe: hvsock connected successfully
[15:31:40.686][ApiProxy ][Info ] Cancel connection…

When it happens Docker won’t pull anything and I need to restart Docker.


(Nicolas Bihan) #2

Just an update, I was able to download one of the large images.
In order to do that I had to disconnect my laptop from its docking station (a Dell D3100).
I tested with direct ethernet connection using the docking station just for my external monitors and I couldn’t get the images downloaded. But when completely unconnected it was successful.
I don’t know too much what to do with this right now. In some way, I think there is a bug only triggered when connected to the docking station.
I will try to find some times to see if I can reproduce when I have an external monitor directly connected to my laptop.

Kind of puzzling…

I am on Windows 10 build 1607 by the way.