[PATCH container] api: mtunnel: fix handling of privileged containers

[PATCH container] api: mtunnel: fix handling of privileged containers

[Fabian Grünbichler]

the unprivileged flag is only set in the config for unprivileged containers,
privileged containers normally simply do not have a value set.

passing an undef value is persisted in the config as

 unprivileged:

which triggers a warning when parsing the config later on.

by only setting the config key in the unprivileged case, the behaviour is
identical to container creation.

Reported in the community forum:
https://forum.proxmox.com/threads/186251/

Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
 src/PVE/API2/LXC.pm | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/PVE/API2/LXC.pm b/src/PVE/API2/LXC.pm
index 42d51a0..5f94d5a 100644
--- a/src/PVE/API2/LXC.pm
+++ b/src/PVE/API2/LXC.pm
@@ -3269,10 +3269,13 @@ __PACKAGE__->register_method({
 
                     eval {
                         my $conf = {
-                            unprivileged => $unprivileged,
                             arch => $arch,
                         };
-                        $rpcenv->check($authuser, '/', ['Sys.Modify']) if !$unprivileged;
+                        if ($unprivileged) {
+                            $conf->{unprivileged} = 1;
+                        } else {
+                            $rpcenv->check($authuser, '/', ['Sys.Modify']);
+                        }
                         PVE::LXC::check_ct_modify_config_perm(
                             $rpcenv,
                             $authuser,
-- 
2.47.3