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

unable to start docker #527

Closed
oberfire opened this issue Sep 6, 2016 · 4 comments
Closed

unable to start docker #527

oberfire opened this issue Sep 6, 2016 · 4 comments

Comments

@oberfire
Copy link

oberfire commented Sep 6, 2016

Expected behavior

Actual behavior

Information

Diagnostic ID: 342FD9EB-70E5-4EA2-9B12-1ACE50E95F42
Docker for Mac: 1.12.0-a (Build 11213)
macOS: Version 10.11.6 (Build 15G31)
[ERROR] docker-cli
docker ps failed
[OK] app
[OK] moby-syslog
[OK] disk
[OK] virtualization
[OK] system
[OK] menubar
[OK] osxfs
[OK] db
[OK] slirp
[OK] moby-console
[OK] logs
[OK] vmnetd
[OK] env
[OK] moby
[OK] driver.amd64-linux

Steps to reproduce

  1. ...
  2. ...
@rscheumann
Copy link

rscheumann commented Sep 6, 2016

the very same here. in the log I found this (syslog -k Sender Docker):

Docker is not responding: Get http://./info: EOF: waiting 0.5s
<Notice>: VM: 2016-09-06 17:58:24 +0000 UTC daemon.info vsudd: 23 Failed to connect to Unix domain socket after 10s /var/run/docker.sock dial unix /var/run/docker.sock: connect: connection refused
<Notice>: VM: 2016-09-06 17:58:25 +0000 UTC daemon.info vsudd: Connection 24 to: 2376 from: 00000000

@mchiang0610
Copy link

Merging with #119

@samoht
Copy link
Contributor

samoht commented Oct 12, 2016

An Assertion failure relating to a Docker component was found in the system logs.

May be related to moby/hyperkit#50

The following log matches:

Aug 31 00:54:29 C02PWAT1G8WN Docker[com.docker.driver.amd64-linux][7480] <Notice>: vcpu 0 waiting for signal to resume
Aug 31 00:54:29 C02PWAT1G8WN Docker[com.docker.driver.amd64-linux][7480] <Notice>: vcpu 3 waiting for signal to resume
Aug 31 00:54:29 C02PWAT1G8WN kernel[kern][0] <Notice>: PM response took 110 ms (7480, com.docker.drive)
Aug 31 00:54:29 C02PWAT1G8WN Docker[com.docker.driver.amd64-linux][7480] <Notice>: vcpu freeze complete: allowing sleep
Aug 31 04:59:17 C02PWAT1G8WN Docker[com.docker.driver.amd64-linux][7480] <Notice>: Assertion failed: (sc->reply_cons != sc->reply_prod), function send_response_common, file src/pci_virtio_sock.c, line 879.
Aug 31 04:59:17 C02PWAT1G8WN Docker[com.docker.driver.amd64-linux][7480] <Notice>: virtio-net-vpnkit: initialising, opts="uuid=846c53bc-13cf-4cb4-a669-7320d23d15da,path=/Users/oberfirer/Library/Containers/com.docker.docker/Data/s50,macfile=/Users/oberfirer/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/mac.0"
Aug 31 04:59:17 C02PWAT1G8WN Docker[com.docker.driver.amd64-linux][7480] <Notice>: Interface will have uuid 846c53bc-13cf-4cb4-a669-7320d23d15da

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jun 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants