Docker Community Forums

Share and learn in the Docker community.

Docker-compose pull failing with read error? (fixed, but reporting)


(Andyburke) #1

Expected behavior

docker-compose pull succeeds

Actual behavior

docker-compose pull locks up extracting image

Information

Version 1.11.1-beta10 (build: 6662)
b4d942b304b7d7d0ee48d96e3b424ccfbcceca89

(I had upgraded automatically through beta 8, beta 9 to beta 10.)

Seeing this in the docker logs:

Docker[69057] <Error>: Socket.TCPV4.read 54.192.85.123:443: caught Unix.Unix_error(Unix.ECONNRESET, "read", "") returning Eof

after docker restart and trying again, same error:

Docker[73014] <Error>: Socket.TCPV4.read 54.192.85.240:443: caught Unix.Unix_error(Unix.ECONNRESET, "read", "") returning Eof

docker-compose pull output stops looking like this:

latest: Pulling from float/rethinkdb
c02c7df4a131: Extracting [===============================================>   ] 33.16 MB/34.87 MB
a3ed95caeb02: Download complete
4acc5a0bbe02: Download complete
e2c4c079e657: Download complete
93563bc74311: Downloading [=======================>                           ] 38.91 MB/81.23 MB
e052b218c423: Downloading [====>                                              ]  2.19 MB/26.29 MB

and another run after restarting docker (note that it is not exactly the same):

latest: Pulling from float/rethinkdb
c02c7df4a131: Extracting [================================================>  ] 33.88 MB/34.87 MB
a3ed95caeb02: Download complete
4acc5a0bbe02: Download complete
e2c4c079e657: Download complete
93563bc74311: Downloading [==========================>                        ] 43.24 MB/81.23 MB
e052b218c423: Downloading [=======>                                           ]  4.14 MB/26.29 MB

pinata diagnose -u before lockup:

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Docker logs are being collected into /tmp/20160504-135756.tar.gz
Most specific failure is: No error was detected
Your unique id is: BDAFB0CA-1CA8-410E-A132-E4452F963466

pinata diagnose -u after lockup:

OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.1-beta10
Running diagnostic tests:
Error docker ps: timeout after 10.00s
[ERROR]   docker-cli       docker ps failed: Misc.Failure
Error docker ps: timeout after 10.00s
Thread 6 killed on uncaught exception Misc.Failure
[OK]      docker-cli
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Error echo "00000003.0000f3a6" | nc -U /var/tmp/com.docker.vsock/connect > /tmp/20160504-135434/diagnostics.tar: timeout after 30.00s
Docker logs are being collected into /tmp/20160504-135434.tar.gz
Most specific failure is: docker ps failed: Misc.Failure
Your unique id is: BDAFB0CA-1CA8-410E-A132-E4452F963466

OSX Version: 10.11.4 (15E65)

Fixed

I noticed that after the Beta9 -> Beta10 upgrade, my docker image cache seemed to have been emptied. Between Beta8 and Beta9 I didn’t have to re-pull any images.

Concerned that something had gone wrong with my install, I did the following:

  1. I uninstalled the Docker for Mac beta from the settings
  2. I re-downloaded the latest (Beta 10) and re-installed
  3. I re-ran docker-compose pull and everything completed successfully

Perhaps there is some issue with the automatic upgrades and the image cache or the osxfs stuff?