When running several containers using compose, it appears the docker daemon quits when it gets very close to using all the allocated memory.
OS X: version 10.11.4 (build: 15E65)
Docker.app: version v1.11.0-beta8.2
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
Apr 20 17:06:10 jbmp Docker[73696] : EOF reading packet from Unix domain socket: closing
Apr 20 17:06:10 jbmp Docker[73696] : Failed to read header
Apr 20 17:06:10 jbmp Docker[73696] : Stopping vmnet interface
Apr 20 17:06:10 jbmp Docker[73692] : Hypervisor subprocess has exitted with code -1
Apr 20 17:06:10 jbmp Docker[72980] : Reap com.docker.driver.amd64-linux (pid 73690): exit status 2
Apr 20 17:06:10 jbmp Docker[72980] : Reap com.docker.driver.amd64-linux (pid 73692): exit status 0
Apr 20 17:06:11 jbmp Docker[72980] : Stop 1 children with order 1: com.docker.driver.amd64-linux (pid 73692)
Apr 20 17:06:11 jbmp Docker[72980] : Stop 2 children with order 2: com.docker.osxfs (pid 73690), com.docker.slirp (pid 73691)
Apr 20 17:06:11 jbmp Docker[72980] : Signal terminated to com.docker.slirp (pid 73691)
Apr 20 17:06:11 jbmp Docker[72980] : Reap com.docker.driver.amd64-linux (pid 73691): signal: terminated
Apr 20 17:06:11 jbmp Docker[72980] : Starting com.docker.osxfs, com.docker.slirp, com.docker.driver.amd64-linux
Apr 20 17:06:11 jbmp Docker[72980] : Start com.docker.osxfs (pid 73934)
Apr 20 17:06:11 jbmp Docker[72980] : Start com.docker.slirp (pid 73935)
Apr 20 17:06:11 jbmp Docker[72980] : Start com.docker.driver.amd64-linux (pid 73936)
Apr 20 17:06:11 jbmp Docker[73696] : Vmnet interface stopped
Apr 20 17:06:11 jbmp Docker[73696] : Vmnet shutdown done
Apr 20 17:06:11 jbmp Docker[73936] : Acquired hypervisor lock
Apr 20 17:06:11 jbmp Docker[73936] : hypervisor: native
Apr 20 17:06:11 jbmp Docker[73936] : filesystem: osxfs
Apr 20 17:06:11 jbmp Docker[73936] : Hypervisor: native; BootProtocol: direct; UefiBootDisk: /Users/johnbarker/UefiBoot.qcow2
Apr 20 17:06:11 jbmp Docker[73936] : Docker is not responding: waiting 0.5s
Apr 20 17:06:11 jbmp Docker[73938] : exec: /Applications/Docker.app/Contents/MacOS/com.docker.driver.amd64-linux string{“-A”, “-m”, “2G”, “-c”, “4”, “-u”, “-s”, “0:0,hostbridge”, “-s”, “31,lpc”, “-s”, “2:0,virtio-ipc,uuid=fa0f1808-4562-4add-a055-0f44b33ec653,path=/var/tmp/com.docker.vmnetd.socket,macfile=/Users/johnbarker/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.0”, “-s”, “3:0,virtio-ipc,uuid=8b051617-213b-474b-984e-ca119694ecb3,path=/var/tmp/com.docker.slirp.socket,macfile=/Users/johnbarker/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.1”, “-s”, “4,virtio-blk,file:///Users/johnbarker/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2”, “-s”, “5,virtio-9p,path=/var/tmp/com.docker.db.socket,tag=db”, “-s”, “6,virtio-rnd”, “-s”, “7,virtio-9p,path=/var/tmp/com.docker.port.socket,tag=port”, “-s”, “8,virtio-sock,guest_cid=3,path=/var/tmp/com.docker.vsock,guest_forwards=2376;1525”, “-l”, “com1,pty=/Users/johnbarker/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty,log=/Users/johnbarker/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring”, “-f”, “kexec,/Applications/Docker.app/Contents/Resources/moby/vmlinuz64,/Applications/Docker.app/Contents/Resources/moby/initrd.img,earlyprintk=serial console=ttyS0 com.docker.driverDir="/Users/johnbarker/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux", com.docker.database="com.docker.driver.amd64-linux"”}
Apr 20 17:06:11 jbmp Docker[73944] : Client reports version 12, commit 3c1bfeb0e86a9403f82302edfea4c4987cc2cb32
Apr 20 17:06:11 jbmp Docker[73944] : com.docker.vmnetd reports MAC address: 22:b9:2e:1e:cf:32
Apr 20 17:06:11 jbmp Docker[73944] : rx batching enabled (len=64)
Apr 20 17:06:14 jbmp Docker[73936] : Docker is not responding: waiting 0.5s
— last message repeated 8 times —
Apr 20 17:06:22 jbmp Docker[73936] : Docker is responding