I observed that a running urunc container loses its running task state after restarting containerd.
Before restarting containerd, the container is shown as running:
root@sev:~/zxd/urunc-per-container# nerdctl -n moby ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fd0b779c7add harbor.nbfc.io/nubificus/urunc/nginx-qemu-linux-raw:latest "/urunit /usr/sbin/n…" 16 seconds ago Up urunc-check-1
After restarting containerd:
root@sev:~/zxd/urunc-per-container# systemctl restart containerd
The same container is reported as Created instead of Up:
root@sev:~/zxd/urunc-per-container# nerdctl -n moby ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fd0b779c7add harbor.nbfc.io/nubificus/urunc/nginx-qemu-linux-raw:latest "/urunit /usr/sbin/n…" 28 seconds ago Created urunc-check-1
In addition, after the container falls back to Created, trying to use nerdctl to stop or kill it through nerdctl does not terminate the existing shim process.
I observed that a running urunc container loses its running task state after restarting containerd.
Before restarting containerd, the container is shown as running:
After restarting containerd:
The same container is reported as Created instead of Up:
In addition, after the container falls back to Created, trying to use nerdctl to stop or kill it through nerdctl does not terminate the existing shim process.