Preconfigured installer variant: skip the first-boot setup wizard #10

Open
opened 2026-07-15 15:14:59 +00:00 by james.oates · 0 comments
Owner

Idea from installed-system testing (2026-07-15): the unattended installer currently lands in Fedora's initial-setup wizard on first boot (language, keyboard, user, hostname, timezone). For some uses we want to pre-answer those at ISO build time so the machine boots straight to a ready login.

Mechanism: bootc-image-builder supports injecting kickstart content, and kickstart has first-class directives for exactly these answers (user, lang, keyboard, timezone, hostname via network). Anaconda's initial-setup skips sections that are already configured — pre-answer everything and the wizard should not appear at all.

Shape: a workflow_dispatch input (or a config file in the repo) feeding a kickstart fragment into the ISO build — producing a personal provisioned ISO alongside the generic one.

Payoffs:

  1. Users/fleet: provision a machine with zero interaction end to end
  2. Testing (the immediate win): a preseeded test ISO (known user + sshd enabled + testbed SSH key in authorized_keys) makes the VM install loop fully automatable — install → boot → SSH in → assert, no human clicking through the wizard. Worth doing for the testbed alone.

Not scheduled; pipeline fundamentals first.

Idea from installed-system testing (2026-07-15): the unattended installer currently lands in Fedora's initial-setup wizard on first boot (language, keyboard, user, hostname, timezone). For some uses we want to pre-answer those at ISO build time so the machine boots straight to a ready login. Mechanism: bootc-image-builder supports injecting kickstart content, and kickstart has first-class directives for exactly these answers (`user`, `lang`, `keyboard`, `timezone`, hostname via `network`). Anaconda's initial-setup skips sections that are already configured — pre-answer everything and the wizard should not appear at all. Shape: a `workflow_dispatch` input (or a config file in the repo) feeding a kickstart fragment into the ISO build — producing a personal provisioned ISO alongside the generic one. Payoffs: 1. **Users/fleet:** provision a machine with zero interaction end to end 2. **Testing (the immediate win):** a preseeded test ISO (known user + sshd enabled + testbed SSH key in authorized_keys) makes the VM install loop fully automatable — install → boot → SSH in → assert, no human clicking through the wizard. Worth doing for the testbed alone. Not scheduled; pipeline fundamentals first.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Glarion/glarion#10
No description provided.