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

Corrupted installation after issuing a docker-compose restart #158

Closed
madmax76 opened this issue Aug 6, 2016 · 3 comments
Closed

Corrupted installation after issuing a docker-compose restart #158

madmax76 opened this issue Aug 6, 2016 · 3 comments

Comments

@madmax76
Copy link

madmax76 commented Aug 6, 2016

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

  1. docker-compose restart
@mchiang0610
Copy link

Merging with #119

@samoht
Copy link
Contributor

samoht commented Oct 12, 2016

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:

Aug  6 18:21:40 mbp-2 Docker[com.docker.driver.amd64-linux][869] <Notice>: Mirage-block error: Unknown write: End_of_file at file /Users/max/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 offset 6209777664 with buffer of length 20480
Aug  6 18:21:40 mbp-2 Docker[com.docker.driver.amd64-linux][869] <Notice>: Docker is not responding: Get http://./info: EOF: waiting 0.5s
Aug  6 18:21:40 mbp-2 Docker[com.docker.driver.amd64-linux][869] <Notice>: Thread 1 killed on uncaught exception Invalid_argument("Cstruct.sub: [0,4096](4096) off=0 len=-31170560")
Aug  6 18:21:40 mbp-2 Docker[com.docker.driver.amd64-linux][869] <Notice>: Docker is not responding: Get http://./info: EOF: waiting 0.5s
Aug  6 18:21:41 mbp-2 Docker[com.docker.driver.amd64-linux][869] <Notice>: Docker is not responding: Get http://./info: EOF: waiting 0.5s
Aug  6 18:21:41 mbp-2 Docker[com.docker.driver.amd64-linux][869] <Notice>: Docker is not responding: Get http://./info: EOF: waiting 0.5s
Aug  6 18:21:42 mbp-2 Docker[com.docker.driver.amd64-linux][869] <Notice>: Docker is not responding: Get http://./info: EOF: waiting 0.5s

@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 18, 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