From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id CB5DC1FF13E for ; Fri, 06 Feb 2026 15:32:26 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8CF3B63E0; Fri, 6 Feb 2026 15:33:00 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Daniel Kral Subject: applied: [PATCH container v2 3/4] setup: add no-op detect_architecture for unmanaged CTs Date: Fri, 6 Feb 2026 15:30:56 +0100 Message-ID: <177038825450.2774896.13854378506080629801.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260206124513.310674-4-d.kral@proxmox.com> References: <20260206124513.310674-1-d.kral@proxmox.com> <20260206124513.310674-4-d.kral@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770388268217 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.020 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: P7XDZUODQRKE3RNDW2ZBW23HBEPOPO6Q X-Message-ID-Hash: P7XDZUODQRKE3RNDW2ZBW23HBEPOPO6Q X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 06 Feb 2026 13:45:04 +0100, Daniel Kral wrote: > This plugin method is only called in PVE::LXC::Setup::new() and is > wrapped in an eval block, so it won't fail to create the container, but > report an error that the plugin method is not implemented for unmanaged > containers. > > Applied but re-ordered this after the next patch, as it cannot really work without the change of 4/4, thanks! [3/4] setup: add no-op detect_architecture for unmanaged CTs commit: 0704ca34c1bb73edcf61bb9aaf22d955cc2cf28b