From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH common/container/manager 0/8] implement per-mountpoint uid/gid mapping
Date: Mon, 23 Feb 2026 14:04:46 +0100 [thread overview]
Message-ID: <20260223130706.90972-1-f.schauer@proxmox.com> (raw)
Add support for configuring UID/GID mappings on individual container
mount points without affecting the global container mapping.
A new "idmap" mount point option accepts space-separated mappings:
```
idmap=type:ct:host:len type:ct:host:len ...
```
type: can be either 'u' or 'g'
ct: ID as seen inside the container
host: corresponding ID on the host
len: number of consecutive IDs to map
Unmapped ranges inherit the container's ID mapping.
Example to pass through the host UID & GID 1005:
```
mp0: /mnt/data,mp=/data,idmap=u:1005:1005:1 g:1005:1005:1
```
This allows, for example, passing through a directory owned by a
specific user on the host to a specific user inside the container,
without changing the ownership on the host or configuring an ID mapping
for the entire container.
Build/Bump order:
* pve-common
* pve-container
* pve-manager
pve-common:
Filip Schauer (3):
tools: export O_CLOEXEC constant
syscall: add missing mount attribute constants
tools: add mount_setattr syscall
src/PVE/Syscall.pm | 3 +++
src/PVE/Tools.pm | 10 ++++++++++
2 files changed, 13 insertions(+)
pve-container:
Filip Schauer (4):
namespaces: relax prototype of run_in_userns
namespaces: refactor run_in_userns
namespaces: add helper to create user namespace from idmap
implement per-mountpoint uid/gid mapping
src/PVE/LXC.pm | 85 ++++++++++++++++++++++++++++++++++++++-
src/PVE/LXC/Config.pm | 7 ++++
src/PVE/LXC/Namespaces.pm | 63 ++++++++++++++++++++++++-----
src/lxc-pve-prestart-hook | 14 +++++++
4 files changed, 157 insertions(+), 12 deletions(-)
pve-manager:
Filip Schauer (1):
ui: lxc/MPEdit: add "idmap" option
www/manager6/lxc/MPEdit.js | 203 +++++++++++++++++++++++++++++++++++++
1 file changed, 203 insertions(+)
Summary over all repositories:
7 files changed, 373 insertions(+), 12 deletions(-)
--
Generated by git-murpp 0.6.0
next reply other threads:[~2026-02-23 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 13:04 Filip Schauer [this message]
2026-02-23 13:04 ` [PATCH common 1/8] tools: export O_CLOEXEC constant Filip Schauer
2026-02-23 13:04 ` [PATCH common 2/8] syscall: add missing mount attribute constants Filip Schauer
2026-02-23 13:04 ` [PATCH common 3/8] tools: add mount_setattr syscall Filip Schauer
2026-02-23 13:04 ` [PATCH container 4/8] namespaces: relax prototype of run_in_userns Filip Schauer
2026-02-23 13:04 ` [PATCH container 5/8] namespaces: refactor run_in_userns Filip Schauer
2026-02-23 13:04 ` [PATCH container 6/8] namespaces: add helper to create user namespace from idmap Filip Schauer
2026-02-23 13:04 ` [PATCH container 7/8] implement per-mountpoint uid/gid mapping Filip Schauer
2026-02-23 13:04 ` [PATCH manager 8/8] ui: lxc/MPEdit: add "idmap" option Filip Schauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260223130706.90972-1-f.schauer@proxmox.com \
--to=f.schauer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox