Description of problem
docker run --rm -d -it --runtime=kata-runtime -v /mnt/tmp:/mnt/tmp:rslave --name bindtest ubuntu
mkdir /mnt/tmp/1
mount --bind /home/disk2/ /mnt/tmp/1/
docker stop bindtest
Expected result
Actual result
kata-runtime: level=warning msg="Could not umount" error="device or resource busy"
$ kata-runtime list
stat /var/lib/docker/overlay2/d0c20d0ddcb11fe9425cd41b169534408c66d4dae440a9df5f50f521a422839c/merged: no such file or directory
$ mount|grep kata|grep tmp
rootfs on /run/kata-containers/shared/sandboxes/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4-9bdadb79490a7796-tmp type rootfs (rw,size=98644776k,nr_inodes=24661194)
/dev/sdc1 on /run/kata-containers/shared/sandboxes/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4-9bdadb79490a7796-tmp/1 type ext4 (rw,noatime,data=ordered)
$ umount /run/kata-containers/shared/sandboxes/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4-9bdadb79490a7796-tmp
umount: /run/kata-containers/shared/sandboxes/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4-9bdadb79490a7796-tmp: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)
$ umount /run/kata-containers/shared/sandboxes/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4-9bdadb79490a7796-tmp/1
$ umount /run/kata-containers/shared/sandboxes/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4/c41e5e992a59422febdaaac348ce4772970cdbb33b539563949cfce697e6e7b4-9bdadb79490a7796-tmp
$
root@ubuntu:~/docker/container# docker run --rm -d -it --runtime=kata-runtime -v /mnt/tmp:/mnt/tmp:rslave --name bindtest ubuntu f4304f7851e8bef0eb31b6e12fdc5ffab619b3083094f9ceec6d8526d3799c76 docker: Error response from daemon: OCI runtime create failed: fork/exec /usr/libexec/kata-containers/kata-shim: Setctty set but Ctty not valid in child: unknown. root@ubuntu:~/docker/container# ls /usr/libexec/kata-containers/ kata-netmon kata-proxy kata-shim kata-shim.bak root@ubuntu:~/docker/container# docker run -tid --runtime kata-runtime busybox bf62a95cf4ec24f65cef8fc4b9d65da6c41062ecd3c356b123cd0d31a7d49974 docker: Error response from daemon: OCI runtime create failed: fork/exec /usr/libexec/kata-containers/kata-shim: Setctty set but Ctty not valid in child: unknown. root@ubuntu:~/docker/container# docker run --rm -it --runtime kata-runtime ubuntu docker: Error response from daemon: OCI runtime create failed: fork/exec /usr/libexec/kata-containers/kata-shim: Setctty set but Ctty not valid in child: unknown. root@ubuntu:~/docker/container#
root@ubuntu:~/docker/container# docker info | grep runtime Runtimes: kata-runtime runc WARNING: No swap limit support root@ubuntu:~/docker/container#