(This is most likely not an autopkgtest bug, but I couldn't determine
the root cause, and this affects autopkgtest so I thought it best to
document it here for those affected, until it can be re-assigned.)
Recently, autopkgtests using unstable images freshly built with
--boot=efi fail to run with:
qemu-system-x86_64: terminating on signal 15 from pid 178300 (/usr/bin/python3)
<VirtSubproc>: failure: timed out waiting for 'login prompt on serial console'
autopkgtest [21:24:02]: ERROR: testbed failure: unexpected eof from the testbed
Exception ignored in: <_io.TextIOWrapper name=6 encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe
Booting the VM manually, systemd hangs and times out waiting for the
following services to start up:
(1 of 2) Job dev-mapper-loop0p1.device/start running (3s / no limit)
(2 of 2) Job dracut-initqueue.service/start running (8s / no limit)
I'm not familiar with early boot initrd environments but the 'loop0p1'
seems suspiciously like something that might have bled in from the host
environment, because vmdb2 uses that during image creation.
Importantly, I noticed that a trixie image build was not affected, so
this shouldn't be related to autopkgtest itself.
Steps to reproduce:
$ sudo autopkgtest-build-qemu --boot=efi unstable /tmp/unstable.img
...
$ autopkgtest -B -U <pkg> -- qemu /tmp/unstable.img
Best,
Christian
Hi Christian, I don't think I am good at helping with qemu issues, but ... If you would have used $(reportbug) than here would have been very useful information about your system, including which suite you run and which versions of dependent packages you run. qemu very recently migrated a new version to testing. Paul
Hi Paul, Indeed, this is a bad habit that I really need to break. I often think the output cannot be relevant and then go the quickest way, but that can turn out to be a poor assumption. In any case, it turns out that this issue stems from the recent -8 revision of dracut in unstable. Building an image with -7 works. Will bisect this, then re-assign. Best, Christian
I can now confirm that it was the dracut 110-8 upload that triggered
this new boot failure. Specifically, it was commit bebb2681, which
added:
fix-dracut-enable-hostonly_cmdline-in-hostonly-mode-again.patch
Disabling this patch fixes the issue for me again.
Reproducing the relevant part from my original report:
Steps to reproduce the autopkgtest failure (should work with any recent
autopkgtest, eg: from trixie):
$ sudo autopkgtest-build-qemu --boot=efi unstable /tmp/unstable-amd64.img
...
$ autopkgtest -B -U dracut -- qemu /tmp/unstable-amd64.img
Interactive image boot:
$ qemu-system-x86_64 \
-enable-kvm \
-drive if=pflash,format=raw,unit=0,read-only=on,file=/usr/share/OVMF/OVMF_CODE_4M.fd \
-device virtio-serial \
-nic user,model=virtio \
-m 2048 \
-smp 2 \
-nographic \
-drive file=/tmp/unstable-amd64.img,discard=unmap,if=virtio
Best,
Christian
So I compared the output of a trixie image build (which continues to successfully EFI boot) and an unstable image build (which exhibits the problem). There is one key difference in the image build log when the kernel gets installed. Here is a snippet from the unstable build: Setting up linux-image-6.19.11+deb14-amd64 (6.19.11-1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.19.11+deb14-amd64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.19.11+deb14-amd64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.19.11+deb14-amd64 I: /initrd.img is now a symlink to boot/initrd.img-6.19.11+deb14-amd64 /etc/kernel/postinst.d/dracut: dracut[W]: Turning off host-only mode: /dev is not mounted! ... The trixie build lacks this dracut warning. So it would appear that in image builds, this problem stems from host-only mode previously being on, and now being turned off. Is this something that can or should be forced/overridden by the image build tool (here, vmdb2 upon which autopkgtest relies)? Best, Christian
Please don't make this something that the image builders have to override. Everytime such a thing gets added, _ALL_ image builders have to re-learn such a thing, and it takes for a long time to update all tools across all platforms where they can possibly run. Think of an image builder running on bookworm, or one running on Fedora, or elsewhere. Please have dracut (or whatever) figure this out automatically. After all it also worked with initramfs-tools. Best, Chris
Those two reports gave me a clue. I assume the opposite. You want hostonly disabled. The patch fix-dracut-enable-hostonly_cmdline-in- hostonly-mode-again.patch enables hostonly-cmdline by default again, but this: dracut[W]: Turning off host-only mode: /dev is not mounted! does not turn off hostonly-cmdline which causes the host config to leak into the initrd. I'll prepare a fix for dracut.
Can you test that this fix solves your issue?
It seems not, I'm afraid. I tested this by first rebuilding -8 with your newest change. Then telling autopkgtest-build-qemu to install these rebuilt packages with the following post-creation script: modscript.sh ~~~~~~~~~~~~ #!/bin/sh # autopkgtest-build-qemu passes the chroot as $1 [ -n "$1" ] || exit 1 cp /tmp/rebuild/*.deb "$1"/ chroot "$1" dpkg -i dracut_110-8_all.deb dracut-core_110-8_amd64.deb dracut-install_110-8_amd64.deb ~~~~~~~~~~~~ $ autopkgtest-build-qemu --script=modscript.sh --boot=efi unstable /tmp/unstable-amd64.img And finally booting with the qemu-system-x86_64 command string that I shared earlier. It still hangs at the same spot, referencing loop0p1. I tested this exact same procedure above with the -7 from snapshot.d.o, and that worked fine, so the procedure itself seems correct. I can also confirm that the warning printed is not relevant, as it also appears in the -7 as I just noticed. It must have been an added after trixie, as extra information. Best, Christian
Apologies, I forgot to turn off wrapping. Correct copy-pastable versions below. modscript.sh ~~~~~~~~~~~~ #!/bin/sh # autopkgtest-build-qemu passes the chroot as $1 [ -n "$1" ] || exit 1 cp /tmp/rebuild/*.deb "$1"/ chroot "$1" dpkg -i dracut_110-8_all.deb dracut-core_110-8_amd64.deb dracut-install_110-8_amd64.deb ~~~~~~~~~~~~ $ autopkgtest-build-qemu --script=modscript.sh --boot=efi unstable /tmp/unstable-amd64.img
``` $ lsinitrd /boot/initrd.img-6.19.11+deb14-amd64 [...] dracut cmdline: root=/dev/mapper/loop77p2 rootfstype=ext4 rootflags=rw,relatime ``` But I verified in a chroot that the patch works as intended (hostonly_cmdline is enabled before but disabled with the patch). We need to further investigate what went wrong in your example. At least I see "Version: dracut-110-9" in the lsinitrd output. So the initrd was regenerated after the package update.
later /dev is mounted: Exec: ['mount', '--bind', '/dev', '/tmp/tmp8sopd0qw/dev'] Exec: ['mount', '--bind', '/sys', '/tmp/tmp8sopd0qw/sys'] Exec: ['mount', '--bind', '/proc', '/tmp/tmp8sopd0qw/proc'] Then your modscript.sh is executed: Processing triggers for dracut (110-9) ... update-initramfs: Generating /boot/initrd.img-6.19.11+deb14-amd64 This time hostonly mode is not disabled, because /dev is mounted.
Thank you for figuring this one out. So my testing methodology was flawed. Unfortunately, I don't know any other way that autopkgtest-build-qemu could be tested, at least not easily (I supposed some --mirror could be hacked). If you are confident enough with the change, that's more than good enough for me. And a -9 upload will enable a regular test. Best, Christian
We believe that the bug you reported is fixed in the latest version of
dracut, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1132794@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Benjamin Drung <bdrung@debian.org> (supplier of updated dracut package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 07 Apr 2026 12:37:12 +0200
Source: dracut
Built-For-Profiles: derivative.ubuntu noudeb
Architecture: source
Version: 110-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Benjamin Drung <bdrung@debian.org>
Closes: 1132794
Launchpad-Bugs-Fixed: 2146342 2147002
Changes:
dracut (110-9) unstable; urgency=medium
.
* update-initramfs: support loading post-update hooks from /usr/share/ too
(LP: #2147002)
* Cherry-pick upstream fixes:
- fix(SYSTEMD-IMPORT): remount /sysroot with dev and suid flags
(LP: #2146342)
- fix(dracut): determine hostonly_cmdline after hostonly setting
(Closes: #1132794)
* Bump Standards-Version to 4.7.4
Checksums-Sha1:
22742146a3e8be92742b4b806023e46c8b8e8cf0 3188 dracut_110-9.dsc
ae22c0d4c8c35b2863b97873c93a74b34029a271 45616 dracut_110-9.debian.tar.xz
914c53858c61800e23e4423cea65d3883de30d1e 8940 dracut_110-9_source.buildinfo
Checksums-Sha256:
6b194a26d585ce3b68a34e310e5c9f6028ec85353c1a87560e929b18ccd0032a 3188 dracut_110-9.dsc
959f65f9c840d09c1690c857651ae9b00177129c37fcf5a2e9e02929efb02436 45616 dracut_110-9.debian.tar.xz
7e2450d944d0aef92c0f420af667613439ae92c1e19fc44fa37067c1aff7daf7 8940 dracut_110-9_source.buildinfo
Files:
7910ffcbb722f3237a96a4e620eecf26 3188 utils optional dracut_110-9.dsc
c404dd096765b1bfd43c119d4a263bfe 45616 utils optional dracut_110-9.debian.tar.xz
2ab909261d57cd0f49b4d64cd6b9bc88 8940 utils optional dracut_110-9_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmnU/mUACgkQFZ61xO/I
d0w20Q//el1H+SGLPj0a5Tfqr1DiUULpcKP0XJnsrzXsboQy+WePdRuoR8xgw6LB
VN/FTSyiNLyPEmwn7Aka1EhKEpp6z8iATB+wssNfO0gI1Grf0zXhcIjWDVgqrcxk
bNC9vDwMVeYiNcycK/qzn6kluDJsymzCbotWo6YJYh2lIEBENveLMmfEcAxfgCPg
JXPp1cnNphAciwtj1uBZLxaYiFfEuH1AJQ6J8SGbL0jl2Y1tjlu4CHwo/qKkeDAO
ARynVwpEi5CQAePwQmY2z6DG2NUMtCJE3qrvnVSzzvctLHLgmYCFrlh/m/lhU4iY
EgIBybTlxYz1NxwT2hIbLBng9jcHykhQd6AeoclKHwPfNzMlNxCF/vwXcxk7G8bw
KXmC6HeoCADpHQnKqrvTH7f07bLke4z/iDBoZkljXtmVl4Dl5/jyiCX6wqqblogU
wr9VggE/wLPJhOzYA8D3A6qYkcQGvHQbFOI3cS/IoEC3XhgcNXRc1VnAbA9UuL7K
6BAvFeBnMkHODTiqDWGCFwP+Xl7w1AnrMptpzVxE6G5WgLg9dk5W/lWMFhMa1Rbk
587uahKu9LDQJCLPsZWTX3aL6dC7BadyVB3dZY14Jfx++7hEEK4z4Q0kOsI/QMd7
RgZ+QIzGr41QDJ+zWPFnuS8qMRp+o6SxlDTvkHRLuh3weaxhndU=
=ykJL
-----END PGP SIGNATURE-----
Control: reopen -1
qemu-system-x86 shows it's again hangs at
(1 of 2) Job dev-mapper-loop0p1.device/start running (3s / no limit)
(2 of 2) Job dracut-initqueue.service/start running (8s / no limit)
I'm very much embarrassed, but I now see that for the autopkgtest
*running*, I repeatedly blind-typed the wrong command. Muscle memory, I
guess... Of course, the runner also needs the EFI option:
$ autopkgtest -B -U dracut -- qemu --boot=efi /tmp/unstable-amd64.img
^^^^
However: the qemu-system-x86_64 command I shared earlier was correct,
and the way I reproduced the two messages from boot above.
Best,
Christian
``` $ sudo autopkgtest-build-qemu --boot=efi unstable /tmp/unstable-amd64.img [...] Exec: ['chroot', '/tmp/tmpyajn1s9p', 'eatmydata', 'apt-get', '-y', '--no-show-progress', '', 'install', 'linux-image-amd64'] [...] Processing triggers for dracut (110-9) ... update-initramfs: Generating /boot/initrd.img-6.19.11+deb14-amd64 dracut[W]: Turning off host-only mode: /dev is not mounted! [...] Exec: ['mount', '--bind', '/dev', '/tmp/tmpyajn1s9p/dev'] Exec: ['mount', '--bind', '/sys', '/tmp/tmpyajn1s9p/sys'] Exec: ['mount', '--bind', '/proc', '/tmp/tmpyajn1s9p/proc'] Exec: ['parted', '-s', '/dev/loop15', 'set', '1', 'esp', 'on'] Exec: ['chroot', '/tmp/tmpyajn1s9p', 'apt-get', 'update'] Hit:1 http://deb.debian.org/debian unstable InRelease Reading package lists... Exec: ['chroot', '/tmp/tmpyajn1s9p', 'apt-get', '-y', '--no-show-progress', 'install', 'grub-efi-amd64'] [...] Processing triggers for dracut (110-9) ... update-initramfs: Generating /boot/initrd.img-6.19.11+deb14-amd64 [...] ``` Then converting the resulting image to raw, mount it and run `lsinitrd` on /boot/initrd.img-6.19.11+deb14-amd64 gives: ``` dracut cmdline: root=/dev/mapper/loop15p2 rootfstype=ext4 rootflags=rw,relatime ``` Explanation: When installing linux-image-amd64, /dev is not mounted and dracut turns off host-only mode. That's what we want for this image. But then /dev gets mounted and the initrd is regenerated (when installing grub-efi-amd6). This time the initrd is build in host-only mode. The big question: How to solve that? Should dracut become smarter and detect either the chroot run or that a loop mount is probably not what is wanted? Or should autopkgtest-build-qemu add a dracut config to disable host-only? This could be done by placing a file in /etc/dracut.conf.d/*.conf with: hostonly="no"
On Wed, Apr 08, 2026 at 11:39:18AM +0200, Benjamin Drung wrote: [..] IMO detection of the chroot is a good approach. We already have various software pieces that behave differently when they detect a chroot (systemctl, glibc postinst, etc). I think this would also help users that run in a rescue environment, as (per my limited understanding), hostonly would also likely produce something that won't boot. As I wrote earlier, I believe this is non-ideal. Each image builder will have to learn it, and each image builder will do something different. You'll end up with various configurations in the wild that you don't know that they exist. Also it seems to me that, once the built installation actually booted, users no longer want the override. Chris
https://github.com/dracut-ng/dracut-ng/pull/2369 In case this patch is applied in dracut, autopkgtest-build-qemu should set this environment variable during the build: DRACUT_EXTRA_ARGS=--no-hostonly
While an option, I'm not entirely sure if autopkgtest is the correct place to do this. The actual image build happens through the lower-level vmdb2, so fixing the problem generally would probably require fixing it in vmdb2. Looping the autopkgtest and vmdb2 maintainers in, in case they see this differently. Best, Christian
Hi, * Christian Kastner [Sat Apr 11, 2026 at 09:41:55AM +0200]: [...] I'd like to highlight and echo Chris' (Hofstaedtler) comment: | As I wrote earlier, I believe this is non-ideal. Each image builder | will have to learn it, and each image builder will do something | different. You'll end up with various configurations in the wild | that you don't know that they exist. *Please* let's avoid a solution for which every single image builder tool needs to special case things. (Speaking with my hat as author of grml-debootstrap (which exists since 2006) and project lead of the Grml rescue live system, and being a previous contributor and maintainer of initramfs-tools. Please don't think about autopkgtest + vmdb2 only, there are *many* image builder tools around.) regards -mika-
We believe that the bug you reported is fixed in the latest version of
dracut, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1132794@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Benjamin Drung <bdrung@debian.org> (supplier of updated dracut package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Mon, 13 Apr 2026 15:34:06 +0200
Source: dracut
Built-For-Profiles: derivative.ubuntu noudeb
Architecture: source
Version: 110-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Changed-By: Benjamin Drung <bdrung@debian.org>
Closes: 1132794
Launchpad-Bugs-Fixed: 2125790 2147471 2148194
Changes:
dracut (110-11) unstable; urgency=medium
.
* Cherry-pick upstream commits:
- fix(dracut): remove leading space from recorded arguments
- fix(dracut): do not record parameters that do not change the initrd
- refactor(70crypt): extract luks_open_interactive into crypt-lib
- feat(overlayfs-crypt): add new encrypted persistent overlay support
(LP: #2125790, #2148194)
- feat(dracut): add a DRACUT_EXTRA_ARGS environment variable
(Closes: #1132794)
- refactor(overlayfs): exit early in case LiveOS_rootfs is mounted
- fix(overlayfs): unmount NEWROOT before mounting overlay (LP: #2147471)
* dracut-core: add new overlayfs-crypt module
* 21-overlayfs autopkgtest: add cryptsetup dependency
Checksums-Sha1:
f33b5a744e2bef5c00e013b90eba39c057e2ec29 3192 dracut_110-11.dsc
ace7e7ffefda7d805294fcb2a17823a734015a2b 55720 dracut_110-11.debian.tar.xz
7d06ffb3570604cff8fe01ca8a53e8dad97fd974 8944 dracut_110-11_source.buildinfo
Checksums-Sha256:
dffdc69fc758f66b5726281ecea29111a013c4195aff4b736494ffe74793ab25 3192 dracut_110-11.dsc
fe4f467fd7f0dec077b21da61291de72496d8bcf3b1c8ebf197d4d14c0807681 55720 dracut_110-11.debian.tar.xz
03a529bbb6a2c1d58b299eaac4639475f7c6029e60ec452746278ea98cb76b15 8944 dracut_110-11_source.buildinfo
Files:
707f53742f85fdc22e54238c2d640854 3192 utils optional dracut_110-11.dsc
7ab098aacc8b82947b4b0d087c76dba2 55720 utils optional dracut_110-11.debian.tar.xz
2527f62b14a0360503eaa04f84169cff 8944 utils optional dracut_110-11_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmnc9vsACgkQFZ61xO/I
d0zSPw/+LAkGaMNAD+4Wuse8x+dEOAo5xpUnbR8IvtLAAB3hgYRyYBgROANgiEJl
mEcquMx5UAlCA0854RCLzyyPROyLeayVCNGY/uuNI5lfRTsRCnMyD5KQYL6OSNgb
b5BTuDW56zuyX3NHxtnjDbz2t7IYZolY0TDtL3TSu3gHhaqxZRzdqv4MYDmI90Vy
9Au3B4TGSNNYQLWRPqesqAYTZ9Xtt2VnVFC7g88AZWKkrxPegUn4sZ/h02VE9MMc
H2I5DRGItIJRx6zeysZKSZIczkXg3TNCgAcbFIyZ9e3EfiThRY65OAV9HlHgIYMN
hrlrGuDSl5ct6Ey1XBYL3tiuRM5Uj24WZoFvbB8lonj7pKK015nKWQ9c233n0LKe
pQEEf4A9Ax0qcJ1Qc4E1D2MNxkC4f5MApr7DhQGGXalNH0VWMqVdA4PJa9X6pDzT
De0cPjV9+AkSCdBQz0L6Vtas0KlzTqtfP55Gl2af9DrseYFVXVIkDyh3OyYWl1zM
6MHRKjNdFqUUtF7C+mayl/lMBefkhtGHErsg1QqabJHZHYbam3bfcfV278xWBqKK
iBXbbeCd+2TJ/t5ma4scxQ/fz2CfpnpL4VwzqQ+R9/hmrSeJ9vBd2cXLsN6H5P8q
zy8UHZPQGi6D9+ALaJ1MqzV8oDgyxPJIRBanWOGAJMIltjVYtNg=
=iTrT
-----END PGP SIGNATURE-----
Control: reopen -1
right, in that it works but is non-ideal.
I tried adding DRACUT_EXTRA_ARGS=--no-hostonly to various parts of
autopkgtest, but did not succeed; the boot still fails at the same spot.
I count at least three occurrences of dracut invocation during an image
build:
(1) when the kernel is installed, a vmdb2 step
(2) when GRUB is installed, a vmdb2 step
(3) somewhere in autopkgtest's post-installation script
("setup-testbed"), where some systemd change seems to fire a
trigger
It's possible that I overlooked something. But in that case, I believe
the above is a good example for how injecting this envvar is a
sub-optimal solution, especially in light of the many other image build
tools out there that might be affected.
I was thinking: perhaps there is a way to restore most of the old
behaviour for the typical image builder use case, while otherwise
enabling the new one.
Specifically, if the root device in question is /dev/loop*, then
automatically use --no-hostonly. and users for which this would be wrong
could set DRACUT_EXTRA_ARGS=--hostonly. So the logic is turned around.
Unless I'm mistaken, this would
(a) "fix" all image builders again
(b) at the cost of doing the wrong thing by default on systems where
/dev/loop* is intentional, but with an option to go around
this.
I'm probably biased, but I'd wager that the (a) use case is much more
likely than the (b) one.
Best,
Christian
Can you show me your patch so that I can reproduce it? * --hostonly is the default * if /dev is not mounted, disable hostonly (thus --no-hostonly) * the hostonly setting influences the default for --hostonly-cmdline This --hostonly-cmdline causes the VM to fail to boot. behaviour? Can we discuss this upstream in https://github.com/dracut-ng/dracut-ng/issues/2355
I'm sorry, but when re-creating the two changes, things now worked. I
suspect that I might have had a typo that escaped even repeated checks.
In this case, the solution was to change (3), specifically by adding
export DRACUT_EXTRA_ARGS=--no-hostonly
to the top of:
/usr/share/autopkgtest/setup-commands/setup-testbed
Even though this could be resolved for the autopkgtest case after all,
as per your instructions, I still have the feeling that this would
remain a challenge for other image builders that could be better
addressed (though again, I'm probably biased).
If you are open to this, sure, though my next opportunity to contribute
will be on Wednesday.
Best,
Christian
Hi, I would like to add another "me too" to what ch and mika said. I am maintaining quite a few "image builders" and just ran into this problem with one of them. This used to work automatically before dracut came along. It can thus evidently be solved automatically. It is an anti-feature to now make all image builders set another environment variable just so that dracut is happy. As ch pointed out, this means that I also have to backport such a change to earlier versions of Debian so that Debian stable or oldstable is able to create a dracut image for testing and unstable. Please fix this problem in one place (in dracut) instead of forcing a lot of maintainers to do busy-work. Thanks! cheers, josch
On Wed, 2026-05-06 at 12:26 +0200, Johannes Schauer Marin Rodrigues wrote: Can you give me psaudo-code or logic how to determine when dracut should default to build a generic initrd and when it can build a host-only initrd?
Hi,
Quoting Benjamin Drung (2026-05-06 14:11:13)
you could use the ischroot command, no?
Usually, chroot checks use something similar to this:
ischroot() {
if [ "$(stat -c "%d/%i" "/")" != "$(stat -Lc "%d/%i" "/proc/1/root" 2>/dev/null)" ]; then
return 0 # in a chroot
fi
return 1 # not in a chroot
}
This checks whether the devicenumber/inode pair of what the process sees as the
root of the filesystem is the same as the one that the process which is currently
PID 1 (init) sees.
The above shell snippet is similar to what used to be used by initramfs-tools
before they switched to using the ischroot tool in 2016 (commit b0a5f26a).
The origin of the snippet might've been the udev postinst where it lived until
2023 when it got switched out in favour of dh_installsystemd.
Thanks!
cheers, josch
On Wed, 2026-05-06 at 12:26 +0200, Johannes Schauer Marin Rodrigues wrote: I submitted this change upstream: fix(dracut): default to hostonly=no in chroot https://github.com/dracut-ng/dracut/pull/2480