Description
Steps to reproduce the issue:
- restart the containerd
- check the containerd logs
Describe the results you received:
restart the containerd by service containerd restart, find the daemon can not started due to below issue:
Jul 12 01:21:07 hchenxa-1 containerd[20061]: containerd: unmounting temp mounts: failed to unmount target /var/lib/containerd/tmpmounts/containerd-mount154886911: device or resource busy
Jul 12 01:21:07 hchenxa-1 systemd[1]: containerd.service: Main process exited, code=exited, status=1/FAILURE
Jul 12 01:21:07 hchenxa-1 systemd[1]: containerd.service: Unit entered failed state.
Jul 12 01:21:07 hchenxa-1 systemd[1]: containerd.service: Failed with result 'exit-code'.
Jul 12 01:21:12 hchenxa-1 systemd[1]: containerd.service: Service hold-off time over, scheduling restart.
Jul 12 01:21:12 hchenxa-1 systemd[1]: Stopped containerd container runtime.
Jul 12 01:21:12 hchenxa-1 systemd[1]: Starting containerd container runtime...
Jul 12 01:21:12 hchenxa-1 systemd[1]: Started containerd container runtime.
Describe the results you expected:
the containerd should be started.
Output of containerd --version:
root@hchenxa-1:~# containerd --version
containerd github.com/containerd/containerd v1.1.0 209a7fc3e4a32ef71a8c7b50c68fc8398415badf
Description
Steps to reproduce the issue:
Describe the results you received:
restart the containerd by service containerd restart, find the daemon can not started due to below issue:
Describe the results you expected:
the containerd should be started.
Output of
containerd --version: