Error response from daemon: driver \"overlay\" failed to remove root filesystem for 805c245dad451542b44bb1b58c60887fa98a64a61f2f0b8de32fa5b13ccc8ce4: remove \/var\/lib\/docker\/overlay\/8f666b802f418f4a3dc4a6cafbefa79afc81491a5cb23da8084dd14e33afbea0\/merged: device or resource busy<\/p><\/blockquote>\n
It usually appears when stopping and starting a container. It results in Docker container not being able to start or starts in a weird dead\/removed state. Issue is presumably fixed in Centos 7.4 as per this github issue<\/a>, but a workaround exists:<\/p>\n 1. Grep by part of ID: Error looks something like Error response from daemon: driver \"overlay\" failed to remove root filesystem for 805c245dad451542b44bb1b58c60887fa98a64a61f2f0b8de32fa5b13ccc8ce4: remove \/var\/lib\/docker\/overlay\/8f666b802f418f4a3dc4a6cafbefa79afc81491a5cb23da8084dd14e33afbea0\/merged: device or resource busy It usually appears when stopping and starting a container. It results in Docker container not being able to start or starts in a weird dead\/removed state. Issue is presumably fixed in Centos […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[20,18],"tags":[],"class_list":["post-218","post","type-post","status-publish","format-standard","hentry","category-linux","category-script-magic"],"_links":{"self":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts\/218","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=218"}],"version-history":[{"count":3,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts\/218\/revisions"}],"predecessor-version":[{"id":537,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=\/wp\/v2\/posts\/218\/revisions\/537"}],"wp:attachment":[{"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=218"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=218"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xpam.pl\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=218"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\ngrep docker \/proc\/*\/mountinfo | grep 8f66<\/code>
\nit shows which process is holding up the mount in busy state
\n\/proc\/31415\/mountinfo:...<\/code>
\n2. Kill the process
\nsudo kill 31415<\/code><\/p>\n
\r\n
\r\n
Cen
\r\nGitHub<\/a>
\r\nEurobattle.net<\/a>
\r\nLagabuse.com<\/a>
\r\nBnetdocs<\/a>
\r\n<\/div>\r\n","protected":false},"excerpt":{"rendered":"