What happens if containerd-shim is killed/dead?

[Random-Liu]

What will happen if containerd-shim is killed/dead?

Based on the current implementation, things will be messed up, and the runc container will be left there.

Based on the TODO, the corresponding container will be cleaned up in next container list.

Does this mean that the client must periodically list containers to drive the cleanup? This is fine, but just want to know the expected behavior.

[mlaventure]

That TODO also applies when containerd receives a SIGCHLD for a shim he created

[Random-Liu]

That TODO also applies when containerd receives a SIGCHLD for a shim he created

Makes sense to me. :)

[crosbymichael]

I'm working on fixing the TODO's here on restore

[zhucan]

@Random-Liu How to check the shim is active?