Package: debootstrap Version: 1.0.123+deb11u1 Severity: normal Dear Maintainer,
after debootstrapping, /etc/machine-id has a regular machine-id as contents which seems suboptimal as its unreproducible and also, and foremost, this can have nasty side-effects... So probably it would be better to either remove the file or write "uninitialized" into it... or support both via commandline flags :) from #debian-devel today: < bluca> for an image builder program, you can do two things with machine-id < bluca> if you want the first boot logic to apply, you can initialize it to "uninitialized" < bluca> if you don't want the first boot logic, have it as an empty file < kibi> I think the behaviour changed between buster and bullseye; not sure what happened since < kibi> (based on my recollection of https://salsa.debian.org/raspi-team/image-specs/-/commit/26a7de63b0bb3de1b5d0c4d0529240721c322dbb for pi images) < Md> | h01ger: when creating an image it is better to have an empty /etc/machine-id than just deleting it, because this way something can bind-mount a writeable file over it in early boot < josch> | h01ger: in case it helps, mmdebstrap writes "uninitialized" to /etc/machine-id < bluca> empty -> no first boot semantics, uninitialized -> first boot semantics < bluca> doc ref for the bug: https://www.freedesktop.org/software/systemd/man/machine-id.html#First%20Boot%20Semantics -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ I'll believe in climate change when Texas freezes over. (Ted Cruz)
signature.asc
Description: PGP signature