Re: [PATCH v2] classes/image-postproc: Enable systemd units based on systemd presets

["'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>]

On Fri, 2025-06-27 at 10:25 +0200, alexander.heinisch via isar-users
wrote:
> From: Alexander Heinisch <alexander.heinisch@siemens.com>
> 
> By default population of the presets is automatically done by systemd
> on first-boot.
> 
> There were several issues with that:
> 
> 1. The rootfs we get as a build artifact does not reflect the actual
> system running in the field.

This might be intentional. We especially need to ensure that things
like the machine-id or ssh keys (machine fingerprint) are not
populated.

> 
> 2. For setups without writeable /etc this fails. With that addition
> it happens already at build time.

We already had bugs in this area (no rw on kernel cmdline) [1] and
discussed with the systemd maintainers (Unfortunately I can't find the
issue...). IIRC the answer was that systemd requires a RW /etc when
transitioning out of the initrd. Having /etc RO is only supported under
some conditions (e.g. after a on-first-boot).

Unfortunately Debian itself does not rely on the systemd on-first-boot
logic, but directly adds the systemd symlinks in /etc - which makes it
inherently incompatible with sd first boot logic.

In general, I prefer to have a concept in ISAR how we want to handle
the first-boot case, instead of papering over the incompatibility of
Debian-install and systemd first boot & vendor-preset over and over
again.

[1] https://groups.google.com/g/isar-users/c/dbxcePqSc04/m/a5y1HgGgBgAJ

Felix


-- 
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/d0cdae46d5084932b25598ad3f621b81742095d0.camel%40siemens.com.