fix: check option['BinaryName'] for runtime absolute path#11557
fix: check option['BinaryName'] for runtime absolute path#11557pacoxu wants to merge 1 commit intocontainerd:mainfrom
Conversation
|
Hi @pacoxu. 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-sigs/prow repository. |
Signed-off-by: Paco Xu <paco.xu@daocloud.io>
|
which version of containerd it's using? I believe we had a fix for this issue which is included in 2.0.3 #11442 |
|
@djdongjin awesome! This was hit in k8s e2e tests, it should be containerd 2.0.x (but kubernetes CI is not straight forward, not sure which patch release). @pacoxu do you understand with confidence which containerd version the tests are using? @djdongjin any chance to backport that PR to the 2.0 branch? |
@rata oh yes it has been backported to 2.0 branch and released in 2.0.3 (backport PR #11446) |
|
Oh, great! |
|
@djdongjin Thanks for the information. We will try to bump containerd to v2.0.3+ then. /close |
kubernetes/test-infra#34510 (comment)
When running pod with usernamespace enabled, there is a failure of runc not found like above.
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-cgroupv2-containerd-node-arm64-e2e-serial-ec2/1901281724340375552
This is a fix try: I am not sure if this is a proper way to check options[binaryname].
@fuweid