all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Filip Schauer <f.schauer@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH container 1/2] make mount point attribute preservation configurable
Date: Wed, 11 Feb 2026 14:49:42 +0100	[thread overview]
Message-ID: <1770817432.uyvsv72z01.astroid@yuna.none> (raw)
In-Reply-To: <20260211110657.50811-2-f.schauer@proxmox.com>

On February 11, 2026 12:06 pm, Filip Schauer wrote:
> 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.
> 
> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>

Reviewed-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>

> ---
>  src/PVE/LXC.pm            | 4 +---
>  src/PVE/LXC/Config.pm     | 6 ++++++
>  src/lxc-pve-prestart-hook | 2 +-
>  3 files changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
> index 41ea991..2c02e9a 100644
> --- a/src/PVE/LXC.pm
> +++ b/src/PVE/LXC.pm
> @@ -2478,10 +2478,8 @@ sub mountpoint_hotplug : prototype($$$$$) {
>          chdir('/')
>              or die "failed to change root directory within the container's mount namespace: $!\n";
>  
> -        my $keep_attrs = $mp->{type} eq 'volume';
> -
>          mountpoint_insert_staged(
> -            $mount_fd, undef, $mp->{mp}, $opt, $root_uid, $root_gid, $keep_attrs,
> +            $mount_fd, undef, $mp->{mp}, $opt, $root_uid, $root_gid, $mp->{keepattrs},
>          );
>      });
>  }
> diff --git a/src/PVE/LXC/Config.pm b/src/PVE/LXC/Config.pm
> index 6f54e9f..0090d61 100644
> --- a/src/PVE/LXC/Config.pm
> +++ b/src/PVE/LXC/Config.pm
> @@ -987,6 +987,12 @@ my $mp_desc = {
>          verbose_description => "Path to the mount point as seen from inside the container.\n\n"
>              . "NOTE: Must not contain any symlinks for security reasons.",
>      },
> +    keepattrs => {
> +        type => 'boolean',
> +        description => 'Inherit attributes from the target path, if it exists already.',

nit: "target path" is not a term we've used here in the past.. the usual
term for this directory is "mountpoint". 

maybe s/target path/mountpoint directory/ here?

_maybe_ we could also spell out what "attributes" means here?

> +        optional => 1,
> +        default => 0,
> +    },
>  };
>  PVE::JSONSchema::register_format('pve-ct-mountpoint', $mp_desc);
>  
> diff --git a/src/lxc-pve-prestart-hook b/src/lxc-pve-prestart-hook
> index f900c12..9862509 100755
> --- a/src/lxc-pve-prestart-hook
> +++ b/src/lxc-pve-prestart-hook
> @@ -100,7 +100,7 @@ PVE::LXC::Tools::lxc_hook(
>                  # Mount relative to the rootdir fd.
>                  $dest_base_fd = $rootdir_fd;
>                  $dest_dir = './' . $mountpoint->{mp};
> -                $keep_attrs = $mountpoint->{type} eq 'volume';
> +                $keep_attrs = $mountpoint->{keepattrs};
>              } else {
>                  # Assert that 'rootfs' is the first one:
>                  die "foreach_mount() error\n" if $opt ne 'rootfs';
> -- 
> 2.47.3
> 
> 
> 
> 
> 
> 




  reply	other threads:[~2026-02-11 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11 11:06 [PATCH container/manager 0/2] " Filip Schauer
2026-02-11 11:06 ` [PATCH container 1/2] " Filip Schauer
2026-02-11 13:49   ` Fabian Grünbichler [this message]
2026-02-11 14:43     ` superseded: " Filip Schauer
2026-02-11 11:06 ` [PATCH manager 2/2] ui: lxc/MPEdit: add "keepattrs" flag Filip Schauer
2026-02-11 13:49   ` 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=1770817432.uyvsv72z01.astroid@yuna.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=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