-
Notifications
You must be signed in to change notification settings - Fork 1.1k
We need to release the SELinux label when we destroy the sandbox #1051
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.
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
Conversation
|
/test all |
|
/test integration_rhel |
|
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, assuming happy tests.
|
/retest |
|
@mrunalp Ooom killer is blowing up on this, I don't see how my PR is related. Any ideas? |
|
Not related, other PRs are failing with that on RHEL |
|
/test integration_rhel |
|
Let's hold on merging this. @runcom is making PRs for his proposed patches. Thanks! |
This will release the MCS Label to be used again. Only do this if we don't have another sandbox using the same label. Also vendor in the latest selinux go bindings, which fixes a leak and properly reserves the SELinux label we are going to use. Signed-off-by: Daniel J Walsh <[email protected]> Signed-off-by: Daniel J Walsh <[email protected]>
|
/test all |
|
Yeah we can get this in if it passes the tests. |
|
@mrunalp Tests pass. Merging. |
This will release the MCS Label to be used again. Only do this if we
don't have another sandbox using the same label.
Also vendor in the latest selinux go bindings, which fixes a leak and
properly reserves the SELinux label we are going to use.
Signed-off-by: Daniel J Walsh [email protected]
Signed-off-by: Daniel J Walsh [email protected]