Fix ctr image mount failing with no such device#12581
Fix ctr image mount failing with no such device#12581AkihiroSuda merged 2 commits intocontainerd:mainfrom
Conversation
Add tests for the WithTemporary mount activation used by `ctr images mount`. Covers bind mount and overlay scenarios to catch regressions like containerd#12549. Signed-off-by: Jérôme Poulin <[email protected]>
The bind mount created for temporary activations was missing the Options field, causing mount to fail with "no such device" because the MS_BIND flag wasn't being set. Fixes containerd#12549 Signed-off-by: Jérôme Poulin <[email protected]>
9b296c1 to
776e50a
Compare
|
@dmcgowan @fuweid , this has been opened and LGTMed by @hsiangkao for a while now. Is there something else holding this up? |
|
/cherry-pick release/2.2 |
|
@AkihiroSuda: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions 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. |
|
@AkihiroSuda: #12581 failed to apply on top of branch "release/2.1": DetailsIn response to this:
Instructions 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. |
|
@AkihiroSuda: new pull request created: #12831 DetailsIn response to this:
Instructions 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. |
|
@AkihiroSuda containerd 2.1 is not impacted. |
The docker-popular-containers pipeline started failing from a regression introduced by containerd v2.2.0. An issue has been lodged on their repo, and the fix has seemingly been merged into the v2.2 branch, we are just waiting on a new release version to pick the fix up. In the meantime, we can disable the faulty plugin mount-manager (which was only introduced in v2.2, so we aren't missing out on anything). Relevant links: - Issue: containerd/containerd#12549 - Fix (main branch): containerd/containerd#12581 - Fix (v2.2 branch): containerd/containerd#12831 Signed-off-by: James Curtis <[email protected]>
The docker-popular-containers pipeline started failing from a regression introduced by containerd v2.2.0. An issue has been lodged on their repo, and the fix has seemingly been merged into the v2.2 branch, we are just waiting on a new release version to pick the fix up. In the meantime, we can disable the faulty plugin mount-manager (which was only introduced in v2.2, so we aren't missing out on anything). Relevant links: - Issue: containerd/containerd#12549 - Fix (main branch): containerd/containerd#12581 - Fix (v2.2 branch): containerd/containerd#12831 Signed-off-by: James Curtis <[email protected]>
Fix for #12549, bind mount missing rbind option.
The bind mount created for temporary activations was missing the Options field, causing mount to fail with "no such device" because the MS_BIND flag wasn't being set.
Test was failing first:
Now success: