Map current user to root in subuid user namespace #3156
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
septatrix
approved these changes
Oct 31, 2024
|
I looked at the fedora:fedora and centos:arch CI and the directory output fails at firstboot during boot. |
DaanDeMeyer
force-pushed
the
subuid
branch
3 times, most recently
from
38aa24f to
2a5cf2c
Compare
By mapping the current user to root in the subuid user namespace, we don't have to change the ownership of all the files in the directory tree to root in the subuid uid/gid range. This means that on btrfs filesystems, we can do a subvolume snapshot instead of an expensive full tree recursion to copy each file individually.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By mapping the current user to root in the subuid user namespace,
we don't have to change the ownership of all the files in the directory
tree to root in the subuid uid/gid range. This means that on btrfs
filesystems, we can do a subvolume snapshot instead of an expensive
full tree recursion to copy each file individually.