Docker disk problem: device or resource busy

Question: [[email protected] ~]# Docker start 01ea65845e45
Error response from Daemon:cannot start container 01ea65845e45:error getting container 01ea65845e4547be24bc3db0bc3b424f AF52B8A0534EB525AA829DD9FD6081C2 from driver devicemapper:error mounting '/dev/mapper/docker-8 : 4-100794844-01ea65845e4547be24bc3db0bc3b424faf52b8a0534eb525aa829dd9fd6081c2 ' on '/var/lib/docker/devicemapper/ MNT/01EA65845E4547BE24BC3DB0BC3B424FAF52B8A0534EB525AA829DD9FD6081C2 ': Device or resource busy
error:failed to start containers: [01ea65845e45]

The above question tells us that the Docker container mounted disk is busy

The same problem-solving experience:

Umount/dev/cdrom/mnt, there have been device or resource busy

The solution is to unload the Mount directory: Umount/dev/cdrom or UMOUNT/MNT

In the same vein, just unload the container's mount directory, and I did it, and it worked. I think that's the problem.

[Email protected] ~]# umount/var/lib/docker/devicemapper/mnt/ 01ea65845e4547be24bc3db0bc3b424faf52b8a0534eb525aa829dd9fd6081c2

[[email protected] ~]# Docker start 01ea65845e45
01ea65845e45
[email protected] ~]# Docker ps-a

CONTAINER id        image                command                 created             STATUS                        ports                                                                       NAMES

01ea65845e45 neo4j "/docker-entrypoint. 2 weeks ago up 4 seconds 0.0.0.0:7272->7473/tcp, 0.0.0.0:7575->7474/TCP, 0.0.0.0:7171->768 7/tcp Romantic_ptolemy

The container after the reboot was successful.

This article is from the "Come Together" blog, please be sure to keep this source http://daxionglaiba.blog.51cto.com/11790757/1812587

Docker disk problem: device or resource busy