-
Notifications
You must be signed in to change notification settings - Fork 324
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
linux: always use direct mapping #1147
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
always use the direct mapping when writing the mappings for an idmapped mount. crun was previously using the reverse mapping, which is not correct and it is being addressed here: containers/crun#1147 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
always use the direct mapping when writing the user namespace for an idmapped mount. This is a breaking change but it is a fairly recent feature and it is only Podman using it. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
e67b316
to
2da0773
Compare
the failure in I'll reenable it once a new crun that contains the current patch gets into a new Fedora build |
@rhatdan PTAL (and containers/podman#17577) |
LGTM |
always use the direct mapping when writing the mappings for an idmapped mount. crun was previously using the reverse mapping, which is not correct and it is being addressed here: containers/crun#1147 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> (cherry picked from commit af8d649)
always use the direct mapping when writing the user namespace for an idmapped mount. This is a breaking change but it is a fairly recent feature and it is only Podman using it.