test: run tests with selinux enforcing #4698
Conversation
|
Hi @dweomer. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Build succeeded.
|
dweomer
force-pushed
the
test-selinux-enforcing
branch
from
3eabf7e to
d7f4d52
Compare
|
Build succeeded.
|
With container-selinux policy updated to 2.145+ (the default for Fedora 32+) we can enable SELinux=Enforcing mode in the CI workflow and pass all integration and CRI tests except one, see containerd#4460, which has been marked as skipped. Tested locally with: - SELINUX=Enforcing vagrant up --provision-with=shell,selinux,test-integration - SELINUX=Enforcing vagrant up --provision-with=shell,selinux,test-cri Signed-off-by: Jacob Blain Christen <[email protected]>
dweomer
force-pushed
the
test-selinux-enforcing
branch
from
d7f4d52 to
a7f24b2
Compare
|
Build succeeded.
|
|
/cc @mikebrow |
|
/ok-to-test |
|
LGTM |
6 participants
With container-selinux policy updated to 2.145+ (the default for Fedora 32+) we
can enable SELinux=Enforcing mode in the CI workflow and pass all integration
and CRI tests except one, see #4460,
which has been marked as skipped.
Tested locally with:
Signed-off-by: Jacob Blain Christen [email protected]