all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container] fix #7603: config: improve verbose description of mountpoint idmap
Date: Tue, 19 May 2026 14:32:10 +0200	[thread overview]
Message-ID: <20260519123212.27281-1-f.schauer@proxmox.com> (raw)

Add more examples for range mapping and passthrough. Use \n\n between
paragraphs to improve readability in generated documentation.

Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
---
 src/PVE/LXC/Config.pm | 20 ++++++++++++--------
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
index c3fbd79..80942d3 100644
--- a/src/PVE/LXC/Config.pm
+++ b/src/PVE/LXC/Config.pm
@@ -377,14 +377,18 @@ my $rootfs_desc = {
         verbose_description =>
             "Customize UID/GID mappings that override the container's `lxc.idmap` for this mount "
             . "point. Accepts a semicolon-separated list of `type:container:disk:range-size` "
-            . "entries.\n"
-            . "`type` is `u` for UID or `g` for GID.\n"
-            . "`container` is the first ID as seen inside the container.\n"
-            . "`disk` is the first corresponding ID on the underlying filesystem.\n"
-            . "`range-size` is the number of consecutive IDs to map.\n"
-            . "Unmapped IDs fall back to the container's `lxc.idmap`.\n"
-            . "Example: `u:123:456:1` maps UID 123 in the container to UID 456 on the disk. "
-            . "Files owned by UID 456 on the disk will appear as UID 123 inside the container.",
+            . "entries.\n\n"
+            . "`type` is `u` for UID or `g` for GID.\n\n"
+            . "`container` is the first ID as seen inside the container.\n\n"
+            . "`disk` is the first corresponding ID on the underlying filesystem.\n\n"
+            . "`range-size` is the number of consecutive IDs to map.\n\n"
+            . "Unmapped IDs fall back to the container's `lxc.idmap`.\n\n"
+            . "Example 1: `u:123:456:1` maps UID 123 in the container to UID 456 on the disk. "
+            . "Files owned by UID 456 on the disk will appear as UID 123 inside the container.\n\n"
+            . "Example 2: `g:100:50:5` maps 5 consecutive GIDs, such that GIDs 100-104 in the "
+            . "container are mapped to GIDs 50-54 on the disk.\n\n"
+            . "Example 3: `passthrough` identity-maps all UIDs and GIDs, meaning IDs inside the "
+            . "container will match the IDs on the disk.",
         format_description =>
             'type:container:disk:range-size[;type:container:disk:range-size;...]',
         pattern =>
-- 
2.47.3





             reply	other threads:[~2026-05-19 12:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 12:32 Filip Schauer [this message]
2026-05-19 20:17 ` applied: [PATCH container] fix #7603: config: improve verbose description of mountpoint idmap Thomas Lamprecht

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=20260519123212.27281-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal