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

Can't connect to docker mac. #505

Closed
jstop opened this issue Sep 2, 2016 · 3 comments
Closed

Can't connect to docker mac. #505

jstop opened this issue Sep 2, 2016 · 3 comments

Comments

@jstop
Copy link

jstop commented Sep 2, 2016

Expected behavior

Docker should respond

Actual behavior

Docker doesn't respond

Information

I did have dlite installed at one point, however I turned it off and uninstalled it. I have no DOCKER in my env.
Diagnostic ID: 7E3FFBC0-2643-4DC1-8F38-194878C5D465
Docker for Mac: 1.12.0-a (Build 11213)
macOS: Version 10.10.5 (Build 14F1909)
[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. ...
@mchiang0610
Copy link

Merging with #119

@samoht
Copy link
Contributor

samoht commented Oct 12, 2016

Detected symptom of problem 'aufs-corruption' in 7E3FFBC0-2643-4DC1-8F38-194878C5D465/20160902-143758.

The daemon cannot start because some files in /var/lib/docker are corrupt. This can happen if the filesystem is unmounted uncleanly. The workaround is to reset to factory defaults which will unfortunately delete /var/lib/docker: all containers and images will need to be rebuilt.

May be related to #20

The following log matches:

time="2016-08-10T14:50:55.952458627Z" level=debug msg="Using default logging driver json-file"
time="2016-08-10T14:50:55.953175531Z" level=debug msg="Golang's threads limit set to 13950"
time="2016-08-10T14:50:55.953703455Z" level=debug msg="[graphdriver] trying provided driver \"aufs\""
time="2016-08-10T14:50:55.958126642Z" level=debug msg="Using graph driver aufs"
time="2016-08-10T14:50:56.202874162Z" level=debug msg="Failed to load mount 2962891d8e0ba572e761fa83eb2394111612852417004816eecf8e278ba21768: invalid mount id value"
time="2016-08-10T14:50:56.209737152Z" level=debug msg="Max Concurrent Downloads: 3"
time="2016-08-10T14:50:56.210031294Z" level=debug msg="Max Concurrent Uploads: 5"
time="2016-08-10T14:50:56.316242778Z" level=info msg="Graph migration to content-addressability took 0.00 seconds"
time="2016-08-10T14:50:56.319205840Z" level=debug msg="Loaded container 0c648f7664901010b6d7b9e8ffd8323cc4faa014829d74556bad5b5f19fe454e"
time="2016-08-10T14:50:56.322710498Z" level=debug msg="Loaded container 19bf3e6daea37201c9a92ed802a26d286b32c3e3881a6145e6631b09e171aa36"

@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