Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Docker Daemon: Error starting daemon : layer does not exist #1808
Container Linux Version
What hardware/cloud provider/hypervisor is being used to run Container Linux?
Running on AWS EC2 instance.
Docker daemon service should run successfully also should heal after reboot.
We are seeing very frequent failure of nodes in our coreos boxes due to docker daemon going into corrupt state .
If we run cleanup corrupted docker images from
This was referenced
Sep 25, 2017
We backported the above referenced patch. It should be available in Container Linux versions >= v1548.0.0 (which means beta now, stable in its next major version).
Apologies for the delay in getting to this; I was hopeful we could upgrade to 1.13+ instead, but per #1930, it looks like we do need to continue maintaining 1.12.
Thanks for reporting the issue, and thanks for the heads up about that patch @cyphar.
I'm experiencing this exact same problem running arch linux on my dev workstation also running arch linux.
Docker consistently fails to start after reboot just like mentioned in previous comments. (I only rebooted twice last month though)
Please note that this is the bug tracker for CoreOS. If you have Arch bugs, please report them to either Arch or upstream. This cause of this bug was very specific and was definitely fixed in