Open prezha opened 5 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
runc 1.1 backport: https://github.com/opencontainers/runc/pull/4231 (will be released in 1.1.13 if/when we do another 1.1.x release)
/remove-lifecycle stale
What Happened?
we see these in some kvm+containerd tests:
example 1:
example 2:
we use runc v1.1.10, and once released, some future version could possibly solve this issue:
(our) runc v1.1.10: https://github.com/opencontainers/runc/blob/18a0cb0f32bcac2ecc9a10f327d282759c144dab/list.go#L131-L134
(latest) runc v1.1.11 - unchanged: https://github.com/opencontainers/runc/blob/4bccb38cc9cf198d52bebf2b3a90cd14e7af8c06/list.go#L131-L134
(current) runc HEAD: https://github.com/opencontainers/runc/blob/0c5a73535503216a8c15a86aa9022d3b0d995994/list.go#L129-L136
so, it's due to a
Possible race with runc delete
interestingly, this change was merged in pr 3379 by @kolyshkin on 2022-01-27, but it looks like it was never released (see the current "runc v1.1.11" above, released on 2024-01-02)
we could simply retry until this gets fixed/released upstream, and then we update to that runc version