public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, o.bektas@proxmox.com
Subject: Re: [pve-devel] [PATCH v2 container] fix #3313: recover unprivileged bit from old config during pct restore
Date: Tue, 23 Feb 2021 15:19:28 +0100	[thread overview]
Message-ID: <661fc659-f655-0d12-51aa-71eeaa4c7989@proxmox.com> (raw)
In-Reply-To: <20210223122936.662855-1-o.bektas@proxmox.com>

Works for me and also fixes the "template restore as non-root" issue 
that apparently nobody complained about.

It was a bit confusing to think about $orig_mp_param, whose assignment 
is now also not guarded by $is_root anymore. But if $orig_mp_param is 
used, i.e. if we enter the

     if ($storage_only_mode) {
         if ($restore) {

block, it's set by a second recover_config() call anyways, so that 
should be fine too.

Reviewed-by: Fabian Ebner <f.ebner@proxmox.com>
Tested-by: Fabian Ebner <f.ebner@proxmox.com>

Am 23.02.21 um 13:29 schrieb Oguz Bektas:
> since pct defaults to privileged containers, it restores the container
> as privileged when `--unprivileged 1` is not passed.
> 
> instead we should check the old configuration and retrieve it
> from there.
> 
> this way, when one creates an unprivileged container on GUI, it will be
> still restored as unprivileged via pct (without having to pass
> `--unprivileged 1` parameter)
> 
> Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> ---
> v1->v2:
> * move the $is_root guard
> * wrap line to make it shorter
> * shorten comment
> * use () around defined
> * also check defined($orig_conf->{unprivileged})
> 
> 
>   src/PVE/API2/LXC.pm | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
> index 8ce462f..3d3dbb0 100644
> --- a/src/PVE/API2/LXC.pm
> +++ b/src/PVE/API2/LXC.pm
> @@ -352,7 +352,7 @@ __PACKAGE__->register_method({
>   		my $orig_mp_param; # only used if $restore
>   		if ($restore) {
>   		    die "can't overwrite running container\n" if PVE::LXC::check_running($vmid);
> -		    if ($is_root && $archive ne '-') {
> +		    if ($archive ne '-') {
>   			my $orig_conf;
>   			print "recovering backed-up configuration from '$archive'\n";
>   			($orig_conf, $orig_mp_param) = PVE::LXC::Create::recover_config($storage_cfg, $archive, $vmid);
> @@ -361,7 +361,11 @@ __PACKAGE__->register_method({
>   			# causing it to restore the raw lxc entries, among which there may be
>   			# 'lxc.idmap' entries. We need to make sure that the extracted contents
>   			# of the container match up with the restored configuration afterwards:
> -			$conf->{lxc} = $orig_conf->{lxc};
> +			$conf->{lxc} = $orig_conf->{lxc} if $is_root;
> +
> +			# make sure to retrieve the privilege level of container if not specified
> +			$conf->{unprivileged} = $orig_conf->{unprivileged} if !defined($unprivileged)
> +			    && defined($orig_conf->{unprivileged});
>   		    }
>   		}
>   		if ($storage_only_mode) {
> 




  reply	other threads:[~2021-02-23 14:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 12:29 Oguz Bektas
2021-02-23 14:19 ` Fabian Ebner [this message]
2021-02-23 14:21 ` Thomas Lamprecht
2021-02-23 14:36   ` Oguz Bektas
2021-02-23 14:49     ` 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=661fc659-f655-0d12-51aa-71eeaa4c7989@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=o.bektas@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal