Hide Forgot
Description of problem: Started docker-latest daemon will start docker-containerd and docker-rhel-push-plugin, but after stopped docker-latest, the other two are still running which caused some problem later on like docker runtime data is still in-use. # systemctl stop docker-latest # rm -rf /var/lib/docker-latest/* rm: cannot remove ‘/var/lib/docker-latest/overlay/dfda124510be24a732abca4b104cc17b7413c3766ddb0972d8dad8fd126fd011/merged’: Device or resource busy # ps aux | grep docker root 11533 0.0 0.0 42772 6984 ? Ssl Aug11 0:00 /usr/libexec/docker/rhel-push-plugin root 11956 0.0 0.1 732948 15232 ? Ssl Aug11 0:25 /usr/libexec/docker/docker-containerd --listen /run/containerd.sock --runtime /usr/libexec/docker/docker-runc --runtime-args --systemd-cgroup=true # systemctl stop docker-containerd # systemctl stop rhel-push-plugin Warning: Stopping rhel-push-plugin.service, but it can still be activated by: rhel-push-plugin.socket # rm -rf /var/lib/docker-latest/* Version-Release number of selected component (if applicable): docker-selinux-1.10.3-46.el7.10.x86_64 docker-common-1.10.3-46.el7.10.x86_64 docker-1.10.3-46.el7.10.x86_64 docker-rhel-push-plugin-1.10.3-46.el7.10.x86_64 docker-latest-1.12.0-4.el7.x86_64 How reproducible: always
Lokesh is this fixed in current docker-latest package?
Reproduced with docker-1.12.6-32.git88a4867.el7.x86_64
*** Bug 1462020 has been marked as a duplicate of this bug. ***
docker-latest is EOL. Closing...