Docker Community Forums

Share and learn in the Docker community.

Mac Beta Crashed during docker-compose up

(Alexellis2) #1

Expected behavior


Compose to go up, services to be on localhost.

Actual behavior

Crash and could not even control + c to close.


 ---> 3ba5c9114339
Removing intermediate container 5c7b22eb1419
Step 6 : RUN mv /app/node_modules /node_modules
 ---> Running in 0070cfb18851
 ---> 84a68b553711
Removing intermediate container 0070cfb18851
Step 7 : ADD . /app
 ---> c35524c8b1af
Removing intermediate container f64d1ebfe53f
Step 8 : ENV PORT 80
 ---> Running in a81506e0e4f5
 ---> e659c7a73e0e
Removing intermediate container a81506e0e4f5
Step 9 : EXPOSE 80
 ---> Running in 06be24d5212e
 ---> cbb823e078f6
Removing intermediate container 06be24d5212e
Step 10 : CMD node server.js
 ---> Running in 1adb45a429df
 ---> 25d006183a51
Removing intermediate container 1adb45a429df
Successfully built 25d006183a51
WARNING: Image for service map-app was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.

^CGracefully stopping... (press Ctrl+C again to force)
^C^C^C^C^C^C^C^C^CERROR: Aborting.
AlexMBA:location-apps alex$ docker-compose up -d
^C^C^CERROR: Aborting.
  • the output of:
    • pinata diagnose -u on OSX
    • DockerDebugInfo.ps1 using Powershell on Windows
  • 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 )
pinata diagnose -u
OS X: version 10.11.4 (build: 15E65) 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
Error exec: echo "00000003.0000f3a6" | nc -U /var/tmp/com.docker.vsock/connect > /tmp/20160426-083919/diagnostics.tar: exit 1
Docker logs are being collected into /tmp/20160426-083919.tar.gz
Most specific failure is: No error was detected
Your unique id is: 4ED262E6-CCCA-4650-A271-25A3CA238825
Please quote this in all correspondence.

Steps to reproduce the behavior

  1. Clone repo above
  2. docker-compose -d up

(David Sheets) #2

I could not reproduce this issue with the same repo and docker-compose up -d.

We are investigating a load-related VSOCK crash that you may have run across. I don’t think a fix will make it into Beta 9 but we are hopeful that it can be resolved for Beta 10.

Thanks for your report and please accept my apologies for this frustrating defect.

Best regards,

David Sheets

(Alexellis2) #3

Looks related to: Docker-compose un-usable on Mac Beta

At the moment I am unable to use docker-compose on my mac, but due to the slowness, but will make use of my Linux box instead.

(Joeblew99) #4

i fixed it, by using this advice.


Now everything is really fast, and no issues at all.