[pve-devel] [PATCH installer v2] auto: allow a binary executable as the first boot executable

[Daniel Kral]

On 12/13/24 11:00, Christoph Heiss wrote:
> The "Automated Installation" page needs to be updated though, to
> reflect:
> 
> a) that either shell-scripts or compiled binaries can be used and
> b) that the compiled binaries must be (obviously) x86_64 and best case
>     statically linked, as there otherwise no guarantees that it will run
>     on the target system and might just fail blindly.

Thanks for taking a second look at this! I've added the following to the 
"Automated Installation" page:

```diff
@@ -233,7 +233,7 @@

  === First Boot Hook Section ===

-Optional. It can be used to configure a script to run on the first boot 
of the new system after a successful installation.
+Optional. It can be used to configure a shell script or a compiled 
binary to run on the first boot of the new system after a successful 
installation.

  If configured, this installs an additional package named 
<code>proxmox-first-boot</code>. After booting the new system for the 
first time, this package can safely be removed using <code>apt purge 
proxmox-first-boot</code>.

@@ -250,6 +250,8 @@

  {{Note| The maximum executable file size is 1 MiB, for both 
integrating it into the ISO and fetching it from a URL.}}

+{{Note| Compiled binaries must target x86_64 Linux and should be 
statically linked, as there are no guarantees for libraries installed on 
the first boot.}}
+
  === Answer File Validation ===

  The <code>proxmox-auto-install-assistant</code> tool can also be used 
to validate the syntax of an answer file and display the identifying 
information that will be sent to the HTTP(s) server when fetching the 
answer file.
```

On 12/13/24 11:00, Christoph Heiss wrote:
> FWIW, just thinking out loud here: Maybe the fetching of the first-boot
> hook should be moved into `proxmox-fetch-answer` altogether. In a sense
> that `proxmox-fetch-answer` would fetch all the needed things in
> advance, such that the auto-installer, post-hook etc. doesn't have to do
> that anymore.
> But that's really not pressing of any kind, rather a long-term thing.

Sounds like a good idea! If you've got other things to do, I can take a 
look at this before the next release for sure.