From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 601C61FF183 for ; Wed, 30 Jul 2025 08:58:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 04B9234382; Wed, 30 Jul 2025 08:59:47 +0200 (CEST) From: Wolfgang Bumiller To: pve-devel@lists.proxmox.com Date: Wed, 30 Jul 2025 08:58:45 +0200 Message-ID: <20250730065911.33062-1-w.bumiller@proxmox.com> X-Mailer: git-send-email 2.47.2 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753858740956 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.075 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [lxc.pm] Subject: [pve-devel] [PATCH container] fix #6573: allow userns creation when nesting is enabled X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" This is another difference with the apparmor 4.0 userspace. We need to explicitly enable user namespaces in the generated profile - at least when nesting is enabled. Signed-off-by: Wolfgang Bumiller --- src/PVE/LXC.pm | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm index 741bb33..b922ba1 100644 --- a/src/PVE/LXC.pm +++ b/src/PVE/LXC.pm @@ -595,6 +595,7 @@ sub make_apparmor_config { # We use abi/4.0 which has its own mqueue class which governs access to /dev/mqueue now. # This is currently not default in lxc's profile, so we enable it explicitly. + # FIXME: once lxc's profiles are based on abi/4.0 this should not be required. $raw .= "lxc.apparmor.raw = allow mqueue,\n"; my @profile_uses; @@ -612,6 +613,8 @@ sub make_apparmor_config { if ($features->{nesting}) { push @profile_uses, 'features:nesting'; $raw .= "lxc.apparmor.allow_nesting = 1\n"; + # FIXME: once lxc's profiles are based on abi/4.0 this should not be required. + $raw .= "lxc.apparmor.raw = allow userns,\n"; } else { # In the default profile in /etc/apparmor.d we patch this in because # otherwise a container can for example run `chown` on /sys, breaking -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel