Allow for a `firstboot.sh` hook script

[schaefi]

Support our customer with a bit more comfort and add a firstboot.sh hook script. If such a script exists kiwi will take the information and turn it into a oneshot systemd unit that gets activated and called on first boot

[schaefi]

Good community statement regarding this idea

Again. I think it's a bad idea to enforce the firstboot actions when there are variations even within distributions.

[schaefi]

• systemd
• cloud-init
• ignition
• ... maybe more

[schaefi]

From a conversation on the Fedora channel we agree on using cloud-init to be a good choice as it is widely adopted and as a framework expected to be distribution agnostic

[Vogtinator]

IMO a systemd unit with ConditionFirstBoot=yes is the best option by far, with cloud-init being the worst by far (way too fat with its dependencies, very slow and known to cause severe issues because it's fairly invasive on its own already)

[Conan-Kudo]

We cannot (solely) use systemd because we cannot assume its existence in kiwi itself. We can assume cloud-init is available, but we cannot assume any other option.

[Vogtinator]

We can assume cloud-init is available

Available maybe, but not used. Pulling in cloud-init just to run some firstboot.sh script is a really bad idea. If it's already part of the image it's probably fine, but not in other cases.

[thkukuk]

We cannot (solely) use systemd because we cannot assume its existence in kiwi itself. We can assume cloud-init is available, but we cannot assume any other option.

Since kiwi converts the script to a systemd one shoot service: we know that systemd will be available, and we know cloud-init will not be available in most cases.

[Conan-Kudo]

We do? I don't recall us having built-in functionality for this.

[Vogtinator]

Me neither - that's what this issue is for AFAIU?

[schaefi]

@thkukuk

Since kiwi converts the script to a systemd one shoot service:

No such functionality exists in kiwi today. That's why we are discussing it. We recently added a new <containers> section which imports locally embedded container archives to the local container registry via a systemd oneshot service. But this functionality is
exclusively connected to the container import feature (see #2663 ) The produced unit file also only has the task to import container archives into the local registry and not more. The feature we are discussing here is an arbitrary firstboot code that gets executed by some system on first boot. What system that should be is basically subject to the conversation

[iammattcoleman]

There's nothing stopping someone from dropping a first-boot script into the filesystem with Kiwi's existing functionality. This seems like it would complicate the configuration syntax for very little practical gain.

[github-actions]

This issue is stale because it has been open 60 days with no activity. stale label was set.