containerd/runtime/v1/shim
Ashray Jain 3e95727f39 Make killing shims more resilient
Currently, we send a single SIGKILL to the shim process
once and then we spin in a loop where we use kill(pid, 0)
to detect when the pid has disappeared completely.

Unfortunately, this has a race condition since pids can be reused causing us
to spin in an infinite loop when that happens.

This adds a timeout to this loop which logs a warning and exits the
infinite loop.

Signed-off-by: Ashray Jain <ashrayj@palantir.com>
2020-06-03 12:57:08 +01:00
..
client Make killing shims more resilient 2020-06-03 12:57:08 +01:00
v1 vendor protobuf & grpc 2020-02-26 10:57:05 +09:00
local.go Runtime v2 2018-07-17 10:21:29 -04:00
service_linux.go Handle large output in v2 shim with TTY 2019-10-11 15:42:05 -04:00
service_unix.go Shim pluggable logging 2019-03-12 12:18:28 -04:00
service.go Avoid allocating slice for finding Process 2020-03-06 09:51:26 -08:00