Disable runc integration tests due to AppArmor issue#1942
Disable runc integration tests due to AppArmor issue#1942k8s-ci-robot merged 1 commit intokubernetes-sigs:masterfrom
Conversation
All runc integration tests are failing in CI due to an AppArmor issue in nested environments. The error occurs when runc tries to access /proc/sys/net/ipv4/ip_unprivileged_port_start, which AppArmor incorrectly interprets as trying to access /sys/... in detached mounts. This is a known issue in runc that affects various container platforms. The maintainers advise against downgrading as the current version fixes multiple container escape vulnerabilities. TODO: Re-enable these tests when a mitigation is found. Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
|
@kubernetes-sigs/cri-tools-maintainers PTAL |
SergeyKanzhelev
left a comment
There was a problem hiding this comment.
/lgtm
/hold
holding in case you want more cri-o contributors to review
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert, SergeyKanzhelev The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/unhold |
|
@saschagrunert The linked issues are resolved: Can we re-enabled this? |
I think so, are you going to propose a PR for that change? |
Yes, I'll create a PR |
|
/revert |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
All runc integration tests are failing in CI due to an AppArmor issue in nested environments. The error occurs when runc tries to access /proc/sys/net/ipv4/ip_unprivileged_port_start, which AppArmor incorrectly interprets as trying to access /sys/... in detached mounts.
This is a known issue in runc that affects various container platforms. The maintainers advise against downgrading as the current version fixes multiple container escape vulnerabilities.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
TODO: Re-enable these tests when a mitigation is found.
Does this PR introduce a user-facing change?