Docker Community Forums

Share and learn in the Docker community.

Machine crash corrupted Docker.qcow2?


(Jamshid) #1

Expected behavior

Machines do sometimes still crash/freeze, especially if they’re a Macbook 12". A crash (spinning beachball after wake, had to force power off) seems to have left my Docker for Mac in a corrupt state, it won’t start up.
A crash should not corrupt the docker installation or lose images.
Ideally I’d be able to restart containers, unless their volumes became corrupt?

Actual behavior

I guess I have to re-init my environment and rebuild/download images.

Information

OS X: version 10.11.4 (build: 15E2066)
Docker.app: version v1.11.1-beta12
Running diagnostic tests:
[OK]      Moby booted
[OK]      driver.amd64-linux
[OK]      vmnetd
[OK]      osxfs
[OK]      db
[OK]      slirp
[OK]      menubar
[OK]      environment
[OK]      Docker
[OK]      VT-x
Error echo "00000003.0000f3a6" | nc -U /Users/jamshid/Library/Containers/com.docker.docker/Data/@connect > /tmp/20160524-212014/diagnostics.tar: timeout after 30.00s
Docker logs are being collected into /tmp/20160524-212014.tar.gz
Most specific failure is: No error was detected
Your unique id is: EE1F66F6-A39C-4932-A729-D93E8A77B4B6
$ syslog -k Sender Docker
May 24 21:16:24 jammb Docker[4418] <Notice>: Starting xhyve
May 24 21:16:24 jammb Docker[4415] <Notice>: May 24 21:16:24  Docker[4418] <Notice>: Starting xhyve
May 24 21:16:24 jammb Docker[4413] <Notice>: PPP.negotiate: received ((magic VMN3T)(version 15)(commit 4151b0fc71e51fb8e551d0a1870893ac99a379bc))
May 24 21:16:24 jammb Docker[4413] <Notice>: PPP.negotiate: received (Ethernet 676a1af7-9c85-4e35-89e6-aec29068a4f7)
May 24 21:16:24 jammb Docker[4413] <Notice>: PPP.negotiate: sending ((mtu 1500)(max_packet_size 1550)(client_macaddr c0:ff:ee:c0:ff:ee))
May 24 21:16:24 jammb Docker[4415] <Notice>: mirage_block_open file:///Users/jamshid/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 buffered = true
May 24 21:16:24 jammb Docker[4413] <Notice>: PPP.listen: called a second time: doing nothing
May 24 21:16:24 jammb Docker[4413] <Notice>: TCP/IP ready
May 24 21:16:24 jammb Docker[4415] <Notice>: mirage_block_open returning 0
May 24 21:16:24 jammb Docker[4415] <Notice>: mirage_block_stat
May 24 21:16:24 jammb Docker[4415] <Notice>: vsock init 7:0 = /Users/jamshid/Library/Containers/com.docker.docker/Data, guest_cid = 3
May 24 21:16:24 jammb Docker[4391] <Notice>: dockerState = running
May 24 21:16:26 jammb Docker[4415] <Notice>: 
	rdmsr to register 0x64e on vcpu 0
May 24 21:16:26 jammb Docker[4415] <Notice>: rdmsr to register 0x34 on vcpu 0
May 24 21:16:26 jammb Docker[4415] <Notice>: Docker is not responding: waiting 0.5s
--- last message repeated 6 times ---
May 24 21:16:29 jammb Docker[4412] <Error>: transfused: mount 
May 24 21:16:29 jammb Docker[4412] <Error>: transfused: /bin/fusermount 
May 24 21:16:29 jammb Docker[4412] <Error>: transfused: -o 
May 24 21:16:29 jammb Docker[4412] <Error>: transfused: allow_other,max_read=1048576,subtype=osxfs 
May 24 21:16:29 jammb Docker[4412] <Error>: transfused: /Mac 
May 24 21:16:29 jammb Docker[4412] <Error>: transfused: 
May 24 21:16:29 jammb Docker[4412] <Notice>: osxfs tracing: OFF 
May 24 21:16:29 jammb Docker[4413] <Notice>: Using protocol TwoThousand msize 8192
May 24 21:16:32 jammb Docker[4415] <Notice>: Thread 1 killed on uncaught exception Invalid_argument("Cstruct.sub: [0,4096](4096) off=0 len=-79564800")
May 24 21:18:35 jammb Docker[4415] <Notice>: sending SIGTERM to com.docker.hyperkit pid 4418
May 24 21:19:21 jammb Docker[4519] <Notice>: EOF reading packet from Unix domain socket: closing
May 24 21:19:21 jammb Docker[4519] <Critical>: Failed to read hello from client
May 24 21:19:21 jammb Docker[4413] <Error>: server loop caught Failure("Caught EOF on underlying FLOW"): no further requests will be processed
--- last message repeated 1 time ---
May 24 21:20:14 jammb Docker[4601] <Notice>: EOF reading packet from Unix domain socket: closing
May 24 21:20:14 jammb Docker[4601] <Critical>: Failed to read hello from client

Steps to reproduce the behavior

  1. But an underpowered, overpriced machine and try to run a docker environment.
  2. Be surprised it works, then try to push it too hard by building and running too much. Close lid for a while, open it, see it freezes when waking.
  3. Exit and reopen the Docker app, do a pinata restart, no errors reported but docker ps just hangs.

(Gabe Marshall) #2

I actually just had this happen to me as well… except I was just running one container and hammering it with thousands of http requests.

OS X: 10.11.3
Docker: 1.11.1-beta13


(Jamshid) #3

Just had this problem happen again. Crash on latest Version 1.12.0-rc2-beta16 (build: 9493) leads to a corrupt docker that never starts.
B3E34FAF-EB15-4959-8049-7657B900A20C