docker pull can be
ctrl-cd and executed again and
docker daemon will continue where it left off.
I’m on Gogo right now (it’s slow and spotty). I try to pull an image. It gets some percentage of the way done and then just stops. If I kill the
docker pull invocation and then try to run it again, it picks up where it left off but it never proceeds further than where I killed it. I have to actually restart Docker in macOS (aka the VM) before it will pull anything. Of course, that starts the layer over, so I’m basically unable to ever get the layer (until I land at least).
- the output of:
Moby Menu > Diagnose & Feedbackon OSX
Docker for Mac: version: mac-v1.11.2-beta15 OS X: version 10.11.5 (build: 15F34) logs: /tmp/20160618-190819.tar.gz failure: No error was detected [OK] docker-cli [OK] app [OK] menubar [OK] virtualization [OK] system [OK] osxfs [OK] db [OK] slirp [OK] moby-console [OK] logs [OK] vmnetd [OK] env [OK] moby [OK] driver.amd64-linux
- a reproducible case if this is a bug, Dockerfiles FTW
- page URL if this is a docs issue or the name of a man page
- host distribution and version ( OSX 10.10.x, OSX 10.11.x, Windows, etc )
OS X 10.11.5 (15F34)
Steps to reproduce the behavior
- Start a docker image pull with fairly slow/spotty internet.
- Wait until the download stalls and stops (even though other Internet works).
- Ctrl-c the docker pull
- Start the docker pull again
- Notice that it doesn’t ever proceed past where it was when you killed it.
It’d be nice if I could open the forums without clobbering my clipboard (re: “Copy diag id to clipboard and open forum” button). Plus this template doesn’t even ask for the Diagnostics ID.
And my Diagnostic ID is 8337D04F-39A8-42F9-83C3-994544794087.