--- Comment #9 from Matthew Heon <mheon(a)redhat.com> ---
It appears I was confused about how to use SIGPROXY - apologies, your original
report was valid.
I can reproduce this on RHEL7 with -SIGSTOP and -SIGCONT, but not with -SIGSTOP
This mainly has to do with the fact that SIGSTOP is not proxied through
--sig-proxy, I believe. SIGSTOP is unmaskable, so the Golang signal handler
can't catch it - the foreground "docker run" process pauses, the background
container does not.
Documentation should be updated to note that Signal 19 is not proxied.
Additionally, I'm attempting to diagnose the issue with Signal 21 being
repeated forever on resume.
You are receiving this mail because:
You are on the CC list for the bug.