This repository was archived by the owner on May 12, 2021. It is now read-only.
docker 19.03: pod information left on /run/vc/ when killing kata hypervisor #2314
Description
Description of problem
While trying to update our supported docker version to 19.03, I see that the hypervisor_stability_kill_test fails as pod information is left under /run/vc/sbs. This does not happen when using docker 18.06.
To reproduce, follow next steps or run the test script above.
fuentess@newdocker:~$ sudo docker run --runtime kata-runtime -tid ubuntu bash
a4ddc2808ed7acf4883397024251fd122990025cf6a7e400a9c166958c010092
fuentess@newdocker:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a4ddc2808ed7 ubuntu "bash" 20 seconds ago Up 16 seconds dreamy_williamson
fuentess@newdocker:~$ pidof qemu-system-x86_64
865
fuentess@newdocker:~$ sudo kill -KILL 865
fuentess@newdocker:~$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fuentess@newdocker:~$ sudo kata-runtime list
WARNING: failed to get container a4ddc2808ed7acf4883397024251fd122990025cf6a7e400a9c166958c010092 rootfs: stat /var/lib/docker/overlay2/f9314de2f862faf78cb3011921c7124d2af6e3e1e4d23c28c5aae791056f96d4/merged: no such file or directory
ID PID STATUS BUNDLE CREATED OWNER
fuentess@newdocker:~$ sudo ls /run/vc/sbs
a4ddc2808ed7acf4883397024251fd122990025cf6a7e400a9c166958c010092
Expected result
pod information on /run/vc/sbs should be deleted by the kata-runtime.
/cc @bergwolf who added the test.
/cc @devimc @jodh-intel @egernst in case they have any idea.