zfs: add idmapped mount support for rootless containers #621
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.
Apply idmapped mounts to ZFS storage layers when UID/GID mappings are
provided. This translates file ownership through the user namespace
mapping, allowing containers to perform chown operations that appear
as root inside the container but map to unprivileged UIDs on the host.
The overlay and btrfs drivers already support idmapped mounts; this
brings ZFS to feature parity for rootless container support.
This works in conjunction with ZFS's zoned_uid property proposed
separately to OpenZFS which delegates dataset operations to user
namespaces, enabling full rootless podman/docker with native ZFS
storage.
Signed-off-by: Colin K. Williams colin@li-nk.org
Resolves #147