On Wed, Jul 29, 2020 at 08:04:54AM +0200, Bastian Blank wrote: > | # /run/systemd/generator/systemd-growfs@-.service > | # Automatically generated by systemd-fstab-generator > | > | [Unit] > | BindsTo=%i.mount > | After=%i.mount > | Before=shutdown.target local-fs.target > > So it is an artefact of Debian being the only distro still starting the > real system with a read-only / (and with that making using first-boot > mode impossible).
This is a systemd upstream issue, fixed in 244.1. See https://github.com/systemd/systemd/issues/14603 and the corresponding fix in https://github.com/systemd/systemd/commit/18e6e8635f06ac8d935ed5494ea65c6dac6af90f The easiest solution for us would be to ship a drop-in configuration fragment to supply the missing dependency. I've opened a merge request to do this at https://salsa.debian.org/cloud-team/debian-cloud-images/-/merge_requests/213 A more complete solution would be to ask the systemd maintainers to backport the above commit to buster, but it's too late to get that change into the upcoming point release (10.5). With that in mind, I propose that we ship the drop-in now, and pursue the systemd fix for buster 10.6. If we get the systemd fix, we can stop shipping the drop-in. noah
