Why "docker rm" fails to remove a dead container on Red Hat Enterprise Linux 7 when a privileged container with bind mount of "/:/rootfs" is running on the host ?

Solution Verified - Updated -

Issue

  • Why 'docker rm' fails to remove a dead container on Red Hat Enterprise Linux 7 when a privileged container with bind mount of "/:/rootfs" is running on the host ?
  • Not able to remove dead containers. Fails with the message " device or resource busy"
docker rm 54787d3579b96121ecf07587acdd494a394506c4cae8e249cdcabb73d03ded6c
Error response from daemon: Unable to remove filesystem for 54787d3579b96121ecf07587acdd494a394506c4cae8e249cdcabb73d03ded6c: remove /var/lib/docker/containers/54787d3579b96121ecf07587acdd494a394506c4cae8e249cdcabb73d03ded6c/shm: device or resource busy
  • Not able to remove stopped container. Fails with the message "Error response from daemon: Driver devicemapper failed to remove root filesystem"
docker rm 758958f915fb
Error response from daemon: Driver devicemapper failed to remove root filesystem 758958f915fb064ed4bef6a64f2d6f50d80f0a677a16ab04c16d527ff7af4a50: failed to remove device 2d4ff8ea74515cafe8789e86137f86cd9cbb3de89bbfeac23d4b277405cdd6b1:Device is Busy

Environment

  • Red Hat Enterprise Linux 7(<= 7.3)
  • Red Hat Enterprise Linux Atomic Host (<= 7.3)
  • docker-1.12.6-32.git88a4867.el7.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content