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

After first install and migrating images from old docker tools, Docker is starting forever #400

Closed
cgagnonqc opened this issue Aug 23, 2016 · 3 comments

Comments

@cgagnonqc
Copy link

Expected behavior

Docker should already be up and running after 15 min.

Actual behavior

Docker is in starting status since 1h

Information

Diagnostic ID: 03E80B4C-6EF1-4363-B662-B536A29051E7
Docker for Mac: 1.12.0-a (Build 11213)
macOS: Version 10.11.3 (Build 15D21)
[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. Have mac with the toolbox for mac installed with several images
    2 install docker for mac
  2. after installation do images migration.
@cgagnonqc cgagnonqc changed the title After first install and migrating images from old docker tools, Docker is starting forever OXS - After first install and migrating images from old docker tools, Docker is starting forever Aug 23, 2016
@cgagnonqc cgagnonqc changed the title OXS - After first install and migrating images from old docker tools, Docker is starting forever OSX - After first install and migrating images from old docker tools, Docker is starting forever Aug 23, 2016
@cgagnonqc cgagnonqc changed the title OSX - After first install and migrating images from old docker tools, Docker is starting forever After first install and migrating images from old docker tools, Docker is starting forever Aug 23, 2016
@mchiang0610
Copy link

Merging with #119

@samoht
Copy link
Contributor

samoht commented Oct 12, 2016

Detected symptom of problem 'daemon-didnt-start' in 03E80B4C-6EF1-4363-B662-B536A29051E7/20160822-202714.

The docker daemon inside the VM failed to start.

The following log matches:

time="2016-08-22T03:09:24.409817895Z" level=debug msg="starting clean shutdown of all containers..."
time="2016-08-22T03:09:24.410639532Z" level=debug msg="Unix socket /run/docker/libnetwork/1df048ccb1862d5eeafb917a20730f8788038ada95b6cc469c67459b0287a158.sock doesn't exist. cannot accept client connections"
time="2016-08-22T03:09:31.759524808Z" level=debug msg="Cleaning up old mountid : start."
time="2016-08-22T03:09:31.760584882Z" level=debug msg="Cleaning up old mountid : done."
time="2016-08-22T03:09:31.761128610Z" level=fatal msg="Error starting daemon: No such container: 8713ef80aa63205dfb6b5f5b3c890d63c769b77341dc43435803f5a3abcd2615"

@justincormack do you know what that docker error means?

@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