From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 74E1A1FF0EC for ; Sat, 07 Nov 2026 19:05:35 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id C265521683; Sat, 07 Nov 2026 19:05:11 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Maximiliano Sandoval Subject: applied: [pve-devel] [PATCH container] fix #6392: setup: fedora: skip --prompt-new-user on firstboot Date: Sat, 7 Nov 2026 19:01:15 +0100 Message-ID: <179407275588.1575726.6865683754352594547.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251219152009.862325-1-m.sandoval@proxmox.com> References: <20251219152009.862325-1-m.sandoval@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: 1794074700580 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.281 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust 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: M32VGOY35LQTEJOWR5DPMZPPLGXWPHQB X-Message-ID-Hash: M32VGOY35LQTEJOWR5DPMZPPLGXWPHQB 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, 19 Dec 2025 16:19:34 +0100, Maximiliano Sandoval wrote: > As per 'homectl --help': > > --prompt-new-user: Query user interactively for user to create > > which will wait on stdin to get the credentials for the new user, but at > this point there is no way for the user to enter such input and the > container will not start. > > [...] Applied, thanks! [1/1] fix #6392: setup: fedora: skip --prompt-new-user on firstboot commit: f994e7b22c770b379f5751e2f94c6ee37306fff6 I reworked this to disable systemd-homed-firstboot.service through the preset we write on every start, as Fabian suggested, instead of overriding its command. That also fixes containers that already got stuck, as their machine-id was never committed and the next start is a first boot again. Adapted the commit message accordingly.