-
Notifications
You must be signed in to change notification settings - Fork 118
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
Corrupted installation after issuing a docker-compose restart #158
Comments
Merging with #119 |
Detected symptom of problem 'qcow2-corruption' in 0EC6304D-EECA-40FA-A211-3A2DC83E7ED5/20160806-182809. This error suggests that the .qcow2 file is corrupt and will need to be recreated. May be related to #11 The following log matches:
|
Closed issues are locked after 30 days of inactivity. 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. |
Expected behavior
Docker to start normally, but after executing
docker-compose restart
my system hang and rebooted.
Actual behavior
after executing
docker-compose restart
my system hang and rebooted.
Running any containers or apps gives the following error:
docker: Error response from daemon: Bad response from Docker engine.
Information
Diagnostic ID: 0EC6304D-EECA-40FA-A211-3A2DC83E7ED5
Docker for Mac: 1.12.0 (Build 10871)
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
The text was updated successfully, but these errors were encountered: