Thank you for taking the time to report this bug and contributing to Ubuntu. I was able to reproduce the issue in a VM installing dracut and systemd-boot. This is what I saw:
1. The kernel postinst calls /etc/kernel/postinst.d/dracut which calls dracut to generate /boot/initrd.img-6.12.0-16-generic 2. /etc/kernel/postinst.d/initramfs-tools calls update-initramfs which calls dracut to generate /boot/initrd.img-6.12.0-16-generic. update-initramfs also calls /etc/initramfs/post-update.d/systemd-boot 6.12.0-16-generic /boot/initrd.img-6.12.0-16-generic 3. /etc/kernel/postinst.d/zz-systemd-boot calls /etc/kernel/postinst.d/zz-systemd-boot 6.12.0-16-generic /boot/vmlinuz-6.12.0-16-generic 4. Then something calls /usr/bin/dracut -f --add-confdir hostonly --kernel-image /boot/vmlinuz-6.12.0-16-generic --no-uefi --kver 6.12.0-16-generic /tmp/kernel-install.staging.Z4Ms72/initrd Further investigation is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100296 Title: Double initrd in /efi/<machine-id>/<kver>/ with systemd-boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2100296/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
