Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App won't start. Communication with networking components failed #2447

Closed
QinMing opened this issue Jan 17, 2018 · 7 comments

Comments

@QinMing
Copy link

commented Jan 17, 2018

Expected behavior

Docker app starts.

Actual behavior

When launching Docker app, I got error message saying "Communication with networking components failed"

Information

Diagnostic ID:
2D9AA290-507E-4D26-9352-3654CE1D1D80

Full output of the diagnostics:

Docker for Mac: version: 17.12.0-ce-mac47 (72b93a017350990850ddc37cd341bd16fce3e911)
macOS: version 10.13.2 (build: 17C205)
logs: /tmp/2D9AA290-507E-4D26-9352-3654CE1D1D80/20180116-223632.tar.gz
failure: No Docker.qcow2 or Docker.raw found: the VM has never been started
[OK]     db.git
[ERROR]  vmnetd
         /var/tmp/com.docker.vmnetd.socket does not exist
         Unexpected error (No such file or directory) connecting to /var/tmp/com.docker.vmnetd.socket
[OK]     dns
[ERROR]  driver.amd64-linux
         com.docker.driver.amd64-linux is not running
[OK]     virtualization VT-X
[OK]     app
[ERROR]  moby
         /Users/ming.qin/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     env
[OK]     virtualization kern.hv_support
[ERROR]  slirp
         Unexpected error ((Failure
  "Error connecting socket to 9p endpoint unix:/Users/ming.qin/Library/Containers/com.docker.docker/Data/s51: Unix.Unix_error(Unix.ENOENT, \"connect\", \"\")")) connecting to /Users/ming.qin/Library/Containers/com.docker.docker/Data/s51
         com.docker.vpnkit is not running
         slirp check failed with: Unix.Unix_error(Unix.ENOENT, "connect", "")
[ERROR]  osxfs
         com.docker.osxfs is not running
[OK]     moby-console
[OK]     logs
[ERROR]  docker-cli
         cannot find docker
         /var/run/docker.sock does not exist
         Unexpected error (No such file or directory) connecting to /var/run/docker.sock
         /Users/ming.qin/Library/Containers/com.docker.docker/Data/s60 does not exist
         Unexpected error (No such file or directory) connecting to /Users/ming.qin/Library/Containers/com.docker.docker/Data/s60
         docker ps failed
[OK]     menubar
[ERROR]  disk
         No Docker.qcow2 or Docker.raw found: the VM has never been started

Screenshots
image
image

Additional Info when running some commands on terminal

$ ls -l /Library/PrivilegedHelperTools/com.docker.vmnetd
-r-xr--r--@ 1 root  wheel  44512 Jan 16 22:49 /Library/PrivilegedHelperTools/com.docker.vmnetd

$ sudo launchctl list | grep com.docker
748	0	com.docker.vmnetd

$ ps uax | grep /Library/PrivilegedHelperTools/com.docker.vmnetd
root               748   0.0  0.0  4298828   4604   ??  Ss   10:49PM   0:00.01 /Library/PrivilegedHelperTools/com.docker.vmnetd

The above seems normal but the following one doesn't look right. As @djs55 said on #644 (comment) , the file /var/tmp/com.docker.vmnetd.socket should exist.

$ ls -l /var/tmp/com.docker.vmnetd.socket                                                                                                                                                                                     10:57:19
ls: /var/tmp/com.docker.vmnetd.socket: No such file or directory

Steps to reproduce the behavior

  1. Installed Docker for Mac and open it.
  2. Type in password as it prompts.
  3. The error will show up.

One day, I quit the Docker app from the menu bar. Since then, I can't start the app again.

Things I have tried

  1. Reboot. Re-install Docker for Mac.
  2. Tried older versions, including 17.09.1-ce-mac42 and 17.06.2-ce-mac27.
  3. Tried removing /Library/PrivilegedHelperTools/com.docker.vmnetd
@QinMing

This comment has been minimized.

Copy link
Author

commented Jan 18, 2018

I tried the test build that @akimd provided in #2452 (comment) , but it didn't help. I also did the factory reset.

Here's the new diagnostics on the test build:

Diagnostic ID: 2D9AA290-507E-4D26-9352-3654CE1D1D80

Docker for Mac: version: 17.12.0-ce-mac49 (72b93a017350990850ddc37cd341bd16fce3e911)
macOS: version 10.13.2 (build: 17C205)
logs: /tmp/2D9AA290-507E-4D26-9352-3654CE1D1D80/20180117-202353.tar.gz
failure: No Docker.qcow2 or Docker.raw found: the VM has never been started
[OK]     db.git
[ERROR]  vmnetd
         /var/tmp/com.docker.vmnetd.socket does not exist
         Unexpected error (No such file or directory) connecting to /var/tmp/com.docker.vmnetd.socket
[OK]     dns
[ERROR]  driver.amd64-linux
         com.docker.driver.amd64-linux is not running
[OK]     virtualization VT-X
[OK]     app
[ERROR]  moby
         /Users/ming.qin/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/console-ring does not exist
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     env
[OK]     virtualization kern.hv_support
[ERROR]  slirp
         Unexpected error ((Failure
  "Error connecting socket to 9p endpoint unix:/Users/ming.qin/Library/Containers/com.docker.docker/Data/s51: Unix.Unix_error(Unix.ENOENT, \"connect\", \"\")")) connecting to /Users/ming.qin/Library/Containers/com.docker.docker/Data/s51
         com.docker.vpnkit is not running
         slirp check failed with: Unix.Unix_error(Unix.ENOENT, "connect", "")
[ERROR]  osxfs
         com.docker.osxfs is not running
[OK]     moby-console
[OK]     logs
[ERROR]  docker-cli
         cannot find docker
         /var/run/docker.sock does not exist
         Unexpected error (No such file or directory) connecting to /var/run/docker.sock
         /Users/ming.qin/Library/Containers/com.docker.docker/Data/s60 does not exist
         Unexpected error (No such file or directory) connecting to /Users/ming.qin/Library/Containers/com.docker.docker/Data/s60
         docker ps failed
[OK]     menubar
[ERROR]  disk
         No Docker.qcow2 or Docker.raw found: the VM has never been started

@akimd

This comment has been minimized.

Copy link
Contributor

commented Jan 18, 2018

Could you please check if the following image fixes your problems? You might need to reset to factory defaults...

https://download-stage.docker.com/mac/pr/21949/Docker.dmg

This is a test build. Ignore any update it might propose, and after testing, reinstall an Edge or Stable version to get proper updates again. Thanks!

@QinMing

This comment has been minimized.

Copy link
Author

commented Jan 18, 2018

@akimd I tried that exact build yesterday. See my previous comment
image

@QinMing

This comment has been minimized.

Copy link
Author

commented Jan 19, 2018

Facepalm. I fixed it myself. It was on me.
I don't have the folder /var/tmp/
So I just sudo mkdir /var/tmp/, and that fixed it.
Maybe Docker app should be more robust about that?

@akimd

This comment has been minimized.

Copy link
Contributor

commented Jan 19, 2018

Can you show me (ls -ld /var/tmp) what owner/rights you gave that directory?

It's kind of funny not to have this directory. I would expect more problems with other software.

@QinMing

This comment has been minimized.

Copy link
Author

commented Jan 19, 2018

This is for the newly created folder
drwxr-xr-x 3 root wheel 96 Jan 18 17:00 /var/tmp

Yaojakey referenced this issue in docker/docker.github.io Jan 19, 2018

Release notes for 17.12.0-ce-mac49 (Stable) (#5787)
* Docker for mac stable relnotes 17.12.0-ce-mac49

Signed-off-by: Jenkins-pr-release-docs <guillaume.tardif@docker.com>
@akimd

This comment has been minimized.

Copy link
Contributor

commented Jan 26, 2018

Closing this issue because there's not much we can do actually (the way services are launched on the Mac allows to create sockets, but not create directories. However:

  • now we have a clean diagnostic when it happens
  • maybe we'll move the socket elsewhere and avoid these issues.

@akimd akimd closed this Jan 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.