Closed kolyshkin closed 2 months ago
Relevant commits/PRs:
This is probably caused by this kernel commit: https://lore.kernel.org/all/20240424132438.514720-1-serein.chengyu@huawei.com/
I.e. the new behavior is right, the old one is wrong. To account for older kernels we have to check both values.
Description
Observed in https://github.com/opencontainers/runc/pull/4370, https://github.com/opencontainers/runc/pull/4360. Was not happening 3 days ago.
Suddenly it fails for me locally, too:
Steps to reproduce the issue
1. 2. 3.
Describe the results you received and expected
no failures
What version of runc are you using?
[kir@kir-tp1 runc]$ ./runc --version runc version 1.2.0-rc.2+dev commit: v1.2.0-rc.2-31-g6602681d spec: 1.2.0 go: go1.22.5 libseccomp: 2.5.5
Host OS information
No response
Host kernel information
No response