-
Notifications
You must be signed in to change notification settings - Fork 814
chroot createPlatformContainer: use MS_REMOUNT #5992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
fd5c2f9
to
12de83d
Compare
@nalind This needs a rebase. |
12de83d
to
fe460bc
Compare
Rebased. |
When setting mount propagation on the root mount before unmounting it, use MS_REBIND, since we know it's already a bind mount, and we actually want to affect the extant bind mount instead of creating another right over it. Otherwise, we might as well have not bothered. Signed-off-by: Nalin Dahyabhai <[email protected]>
fe460bc
to
699c84d
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flouthoc, nalind The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
5b8423e
into
containers:main
/cherry-pick release-1.39 |
@nalind: #5992 failed to apply on top of branch "release-1.39":
In 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. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
When setting mount propagation on the root mount before unmounting it, use
MS_REBIND
, since we know it's already a bind mount, and we actually want to affect the extant bind mount instead of creating another right over it. Otherwise, we might as well have not bothered.How to verify it
New integration test!
Which issue(s) this PR fixes:
Related to KONFLUX-5871.
Special notes for your reviewer:
Does this PR introduce a user-facing change?