899b4e3cb5
Starting with go1.14, the go runtime hijacks SIGURG but with no way to not send to other signal handlers. In practice, we get this signal frequently. I found this while testing out go1.15 with ctr and multiple execs with only `echo hello`. When the process exits quickly, if the previous commit is not applied, you end up with an error message that it couldn't forward SIGURG to the container (due to the process being gone). Signed-off-by: Brian Goff <cpuguy83@gmail.com> |
||
|---|---|---|
| .. | ||
| containerd | ||
| containerd-shim | ||
| containerd-shim-runc-v1 | ||
| containerd-shim-runc-v2 | ||
| containerd-stress | ||
| ctr | ||
| gen-manpages | ||
| protoc-gen-gogoctrd | ||