Restarting the Docker service at run time may cause container to fail to start, and the error message is similar to the container
Error response from Daemon:cannot start container zookeeper:error getting container DDF1DD91BBF46DC648268327F8F7C6FFFAF 2F19CDA5CF1D97FDC701016D4332C from driver devicemapper:error mounting '/dev/mapper/docker-8:1-525372- ddf1dd91bbf46dc648268327f8f7c6fffaf2f19cda5cf1d97fdc701016d4332c ' on '/var/lib/docker/devicemapper/mnt/ DDF1DD91BBF46DC648268327F8F7C6FFFAF2F19CDA5CF1D97FDC701016D4332C ': Device or resource busy2015/01/2604:42:07 Error: Failed Tostart one or more containers
This is a Docker bug .
The solution is to first find the path without unmount
cat/proc/mounts | grep "Mapper/docker" | awk ' {print $} '
Then unmount in turn
This article is from the "Last Night Rain Wind Sudden" blog, please be sure to keep this source http://zxx287856774.blog.51cto.com/3417296/1811730
Container restarting the Docker service while it is running may cause container to fail to start