Docker Community Forums

Share and learn in the Docker community.

Docker mac-v1.12.0-beta17 locks up after docker-compose operations


(Badevguru) #1

Summary

Docker had been working fine. Something managed to lock up the entire docker daemon with a Failure "Caught EOF on underlying FLOW" error.

On side note, the upload feature of the diagnostics is not working.

Expected behavior

Docker compose up command works without error

Actual behavior

Get:

ERROR: for dives-api  Bad response from Docker engine
ERROR: Encountered errors while bringing up the project.

Information

  • the output of:
    • Moby Menu > Diagnose & Feedback on OSX
Docker for Mac: version: mac-v1.12.0-beta17
OS X: version 10.11.5 (build: 15F34)
logs: /tmp/20160705-125403.tar.gz
failure: docker ps failed: Failure("docker ps: timeout after 10.00s")
[ERROR]  docker-cli
         docker ps failed
[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

This happened once. Recording everything to help troublshoot in the future.

  • 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 )

  • From syslogs on OS/X:

7/5/16 12:51:14.909 PM Docker[2643]: Creating resource Entry(tcp:0.0.0.0:32781:tcp:172.23.0.2:28015)
7/5/16 12:51:14.911 PM Docker[2643]: Write offset=0 data=[tcp:0.0.0.0:32781:tcp:172.23.0.2:28015] to file
7/5/16 12:51:14.911 PM Docker[2643]: attempting a best-effort bind of ::1:32781
7/5/16 12:51:14.911 PM Docker[2643]: Created instance tcp:0.0.0.0:32781:tcp:172.23.0.2:28015
7/5/16 12:51:14.965 PM Docker[2643]: Creating resource Entry(tcp:0.0.0.0:32782:tcp:172.23.0.2:8080)
7/5/16 12:51:14.966 PM Docker[2643]: Write offset=0 data=[tcp:0.0.0.0:32782:tcp:172.23.0.2:8080] to file
7/5/16 12:51:14.967 PM Docker[2643]: attempting a best-effort bind of ::1:32782
7/5/16 12:51:14.967 PM Docker[2643]: Created instance tcp:0.0.0.0:32782:tcp:172.23.0.2:8080
7/5/16 12:51:15.029 PM Docker[2643]: Creating resource Entry(tcp:0.0.0.0:28015:tcp:172.23.0.3:28015)
7/5/16 12:51:15.031 PM Docker[2643]: Write offset=0 data=[tcp:0.0.0.0:28015:tcp:172.23.0.3:28015] to file
7/5/16 12:51:15.031 PM Docker[2643]: attempting a best-effort bind of ::1:28015
7/5/16 12:51:15.031 PM Docker[2643]: Created instance tcp:0.0.0.0:28015:tcp:172.23.0.3:28015
7/5/16 12:51:15.095 PM Docker[2643]: Creating resource Entry(tcp:0.0.0.0:32783:tcp:172.23.0.3:28015)
7/5/16 12:51:15.097 PM Docker[2643]: Write offset=0 data=[tcp:0.0.0.0:32783:tcp:172.23.0.3:28015] to file
7/5/16 12:51:15.097 PM Docker[2643]: attempting a best-effort bind of ::1:32783
7/5/16 12:51:15.097 PM Docker[2643]: Created instance tcp:0.0.0.0:32783:tcp:172.23.0.3:28015
7/5/16 12:51:15.144 PM Docker[2643]: Creating resource Entry(tcp:0.0.0.0:8080:tcp:172.23.0.3:8080)
7/5/16 12:51:15.145 PM Docker[2643]: Write offset=0 data=[tcp:0.0.0.0:8080:tcp:172.23.0.3:8080] to file
7/5/16 12:51:15.146 PM Docker[2643]: attempting a best-effort bind of ::1:8080
7/5/16 12:51:15.146 PM Docker[2643]: Created instance tcp:0.0.0.0:8080:tcp:172.23.0.3:8080
7/5/16 12:51:15.197 PM Docker[2643]: Creating resource Entry(tcp:0.0.0.0:32784:tcp:172.23.0.3:8080)
7/5/16 12:51:15.199 PM Docker[2643]: Write offset=0 data=[tcp:0.0.0.0:32784:tcp:172.23.0.3:8080] to file
7/5/16 12:51:15.199 PM Docker[2643]: attempting a best-effort bind of ::1:32784
7/5/16 12:51:15.199 PM Docker[2643]: Created instance tcp:0.0.0.0:32784:tcp:172.23.0.3:8080
7/5/16 12:53:06.655 PM Docker[2643]: server loop caught (Failure "Caught EOF on underlying FLOW"): no further requests will be processed
7/5/16 12:53:06.693 PM Docker[9845]: EOF reading packet from Unix domain socket: closing
7/5/16 12:53:06.699 PM Docker[9845]: Failed to read hello from client
7/5/16 12:53:16.076 PM Docker[2643]: server loop caught (Failure "Caught EOF on underlying FLOW"): no further requests will be processed
7/5/16 12:53:16.076 PM Docker[9866]: EOF reading packet from Unix domain socket: closing
7/5/16 12:53:16.076 PM Docker[9866]: Failed to read hello from client
7/5/16 12:53:38.077 PM Docker[2643]: TCP 104.239.220.248:80 > 192.168.65.2:41934 proxy failed with flow proxy b: Connection refused
7/5/16 12:53:43.497 PM Docker[2643]: TCP 104.239.220.248:80 > 192.168.65.2:41944 proxy failed with flow proxy b: Connection refused
7/5/16 12:54:14.263 PM Docker[2643]: server loop caught (Failure "Caught EOF on underlying FLOW"): no further requests will be processed
7/5/16 12:54:14.284 PM Docker[9968]: EOF reading packet from Unix domain socket: closing
7/5/16 12:54:14.297 PM Docker[9968]: Failed to read hello from client

Steps to reproduce the behavior

Don’t know if this is recreatable. But captured this information when it happened in case it helps.

docker-compose up -d
Creating network "data_default" with the default driver
Creating data_rethinkdb_1
Creating data_rethinkdb_seed_1
Creating data_dives-api_1

ERROR: for dives-api  Bad response from Docker engine
ERROR: Encountered errors while bringing up the project.