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 D8C9F1FF141 for ; Fri, 30 Jan 2026 16:15:36 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 37A70156A; Fri, 30 Jan 2026 16:16:00 +0100 (CET) From: Maximiliano Sandoval To: Fabian =?utf-8?Q?Gr=C3=BCnbichler?= Subject: Re: [pve-devel] [PATCH container] fix #6392: setup: fedora: skip --prompt-new-user on firstboot In-Reply-To: <1768486661.9u9pts34rj.astroid@yuna.none> ("Fabian =?utf-8?Q?Gr=C3=BCnbichler=22's?= message of "Thu, 15 Jan 2026 15:19:58 +0100") References: <20251219152009.862325-1-m.sandoval@proxmox.com> <1768486661.9u9pts34rj.astroid@yuna.none> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Fri, 30 Jan 2026 16:15:25 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1769786056898 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.089 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 Message-ID-Hash: ZFM2QLGSCKCCD4BDDIUVB2FWOENWK62A X-Message-ID-Hash: ZFM2QLGSCKCCD4BDDIUVB2FWOENWK62A X-MailFrom: m.sandoval@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 CC: Proxmox VE development discussion X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Fabian Gr=C3=BCnbichler writes: > On December 19, 2025 4:19 pm, Maximiliano Sandoval wrote: >> As per 'homectl --help': >>=20 >> --prompt-new-user: Query user interactively for user to create >>=20 >> 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. >>=20 >> One could alternatively remove the unit file from the >> 'systemd-firstboot(1)' step, but this incantation has valid use-cases >> like recognizing a existing homes on firstboot. > > 1. this makes no sense in the commit message ;) > 2. I don't think homed integration makes a lot of sense for a system > container, and would rather skip it altogether I would say it is up to the user. Someone might use this for some service to quickly populate their config/state or create new users for services with systemd credentials, I would prefer not to disable this option if it can be so easily patched to not require stdin. --=20 Maximiliano