public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container] fix #6392: setup: fedora: skip --prompt-new-user on firstboot
Date: Fri, 30 Jan 2026 16:15:25 +0100	[thread overview]
Message-ID: <s8objibcesy.fsf@proxmox.com> (raw)
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")

Fabian Grünbichler <f.gruenbichler@proxmox.com> writes:

> On December 19, 2025 4:19 pm, 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.
>> 
>> 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.

-- 
Maximiliano




      reply	other threads:[~2026-01-30 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 15:19 Maximiliano Sandoval
2026-01-15 14:19 ` Fabian Grünbichler
2026-01-30 15:15   ` Maximiliano Sandoval [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s8objibcesy.fsf@proxmox.com \
    --to=m.sandoval@proxmox.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal