How is this something relied on for building images? As it stands, such a boot entry is non functional since it doesn't tell grub to set up a loop mapping to the underlying file so the "disk" won't be found. If you are building an image and later transferring that image to bare metal, then it would work ( who does this? ), but does that use case only need to get the running system set up, or does it also need to be able to have os-prober add entries for other installations too?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788775 Title: updating grub can end up with loopback devices in grub.cfg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788775/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
