Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to stop containers running systemd with SIGRTMIN+3 #1766

Closed
sajones opened this issue Mar 26, 2018 · 3 comments
Closed

Unable to stop containers running systemd with SIGRTMIN+3 #1766

sajones opened this issue Mar 26, 2018 · 3 comments

Comments

@sajones
Copy link

sajones commented Mar 26, 2018

The version of runc provided by CentOS, based on RC4 it appears, returns unknown signal "RTMIN+3" or unknown signal "37" when I attempt it send the systemd prescribed shutdown signal. The earlier version of runc I have available is based on RC2-dev commit c91b5be and does not exhibit this issue. The older version did not accept the signal by name, however it did allow sending the signal by its number, 37, instead.
@crosbymichael
Copy link
Member

crosbymichael commented Mar 26, 2018 •
edited
Loading

Are you using runc kill for this? Can you paste the command you are running?

@sajones
Copy link
Author

sajones commented Mar 26, 2018 •
edited
Loading

runc kill <container-id> 37 works on RC2 and breaks in RC3 and later. runc kill <container-id> RTMIN+3 does not work in any version.

@sajones
Copy link
Author

sajones commented Mar 26, 2018

After more commit testing it appears the issue was introduced with a367e4b and resolved by 7ac503d. While sending raw signal numbers to runc kill it appears to be the only way using runc to stop a container started by runc that uses systemd as the container PID 1. Since 7ac503d is part of RC5 will close this issue.

@sajones sajones closed this as completed Mar 26, 2018
robertgzr added a commit to balena-os/balena-engine that referenced this issue Feb 25, 2019
@robertgzr
vendor: Update runc to include fix for opencontainers/runc#1766
69c9ab0 
Change-type: patch
Signed-off-by: Robert Günzler <robertg@balena.io>
robertgzr added a commit to balena-os/balena-engine that referenced this issue Feb 25, 2019
@robertgzr
vendor: Update runc to include fix for opencontainers/runc#1766
ad1ae96 
Change-type: patch
Signed-off-by: Robert Günzler <robertg@balena.io>
robertgzr added a commit to balena-os/balena-engine that referenced this issue Feb 25, 2019
@robertgzr
Merge pull request #147 from balena-os/kill-sigs
76a7c11 
vendor: Update runc to include fix for opencontainers/runc#1766
agherzan pushed a commit to balena-os/meta-balena that referenced this issue Feb 25, 2019
balena-engine: Update to include fix for signal SIGRTMIN+3
a675218 
See: opencontainers/runc#1766

Change-type: patch
Signed-off-by: Andrei Gherzan <andrei@balena.io>
@agherzan agherzan mentioned this issue Feb 25, 2019
Merged
4 tasks
agherzan pushed a commit to balena-os/meta-balena that referenced this issue Feb 27, 2019
balena-engine: Update to include fix for signal SIGRTMIN+3
0e19efb 
See opencontainers/runc#1766.

Change-type: patch
Signed-off-by: Andrei Gherzan <andrei@balena.io>
@lion7 lion7 mentioned this issue Mar 5, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@crosbymichael @sajones