mirror of
https://github.com/flatcar/scripts.git
synced 2025-08-18 10:27:00 +02:00
When Docker/containerd binaries are compiled with Go 1.15 the containers generate many signal 23 (SIGURG) events which flood monitoring systems: https://github.com/kubernetes/kops/issues/10388 The SIGURG signal does not kill the process but is generated by Go runtime scheduling: https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md) Because the Go runtime does not know if the process expects external SIGURG signals, the signal is not filtered out but reported to the process: https://github.com/golang/go/issues/37942 The process has to filter this signal out itself before forwarding it to, e.g,. children processes or logs. This change was introduced with the Go 1.15 update (actually Go 1.14 but Flatcar skipped that for Stable), however, while containerd has some workarounds in place, e.g., in https://github.com/containerd/containerd/pull/4532 but there are still areas where the signal is not handled correctly. Until this is the case, downgrade to use the Go 1.13 compiler for Docker/containerd binaries. See https://github.com/kinvolk/Flatcar/issues/315 |
||
---|---|---|
.. | ||
src/third_party/coreos-overlay |