From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH container/manager v2 0/2] make mount point attribute preservation configurable
Date: Wed, 11 Feb 2026 15:41:08 +0100 [thread overview]
Message-ID: <20260211144111.123837-1-f.schauer@proxmox.com> (raw)
The commit 0db559517ac6 (mountpoint_insert_staged: inherit attributes if
directory already exists) introduced automatic propagation of uid, gid,
and mode from the target directory to the mounted filesystem. While this
improves compatibility with some OCI images, it also caused undesired
ownership changes on some mount points.
Since attribute preservation is not always desired, make this behavior
configurable via a new "keepattrs" mountpoint flag. Default to disabled
to preserve historical behavior.
Patch 2/2 exposes this flag in the UI and depends on patch 1/2.
Changed since v1:
* Improve descriptions of new "keepattrs" flag
pve-container:
Filip Schauer (1):
make mount point attribute preservation configurable
src/PVE/LXC.pm | 4 +---
src/PVE/LXC/Config.pm | 9 +++++++++
src/lxc-pve-prestart-hook | 2 +-
3 files changed, 11 insertions(+), 4 deletions(-)
pve-manager:
Filip Schauer (1):
ui: lxc/MPEdit: add "keepattrs" flag
www/manager6/lxc/MPEdit.js | 15 +++++++++++++++
1 file changed, 15 insertions(+)
Summary over all repositories:
4 files changed, 26 insertions(+), 4 deletions(-)
--
Generated by git-murpp 0.6.0
next reply other threads:[~2026-02-11 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 14:41 Filip Schauer [this message]
2026-02-11 14:41 ` [PATCH container v2 1/2] " Filip Schauer
2026-02-11 14:41 ` [PATCH manager v2 2/2] ui: lxc/MPEdit: add "keepattrs" flag Filip Schauer
2026-02-12 14:31 ` applied-series: [PATCH container/manager v2 0/2] make mount point attribute preservation configurable Fabian Grünbichler
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=20260211144111.123837-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.