-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dracut 056 breaks gui image building due to systemd module dependency #296
Comments
I tested it and have the same issue. Apparently the problem is NetworkManager. I tried to remove it from ISO and it built successfully. I replaced it by Connman in my custom ISOs. |
well the problem is with the dbus-daemon hook wanting the systemd hook, but it's pulled in because network-manager is pulled in |
This reverts commit 7def67b. dracut 056 causes a regression in live images because the network-manager hook depends on the systemd hook now (void-linux/void-mklive#296)
Can you try if adding this lines to the dracut.conf makes it work again ?
known issue upstream: https://github.com/dracutdevs/dracut/issues?q=is%3Aissue+is%3Aopen+dbus-daemon
|
from the linked issue, network-legacy is going away, to prefer iwd or networkmanager. |
New dracut update fails when building initramfs for live ISO when NetworkManager is present, as it now depends on systemd hook. Void Linux didn't take a decision yet about what they'll do about this, but we decided to nip the problem in the bud dropping NetworkManager in favor of Connman. connman-gtk GUI was chosen even for Qt desktop environments, because is easier to understand for new users than cmst. Fixes void-linux#296.
This reverts commit 7def67b. dracut 056 causes a regression in live images because the network-manager hook depends on the systemd hook now (void-linux/void-mklive#296)
@classabbyamp Seeing that you merged the downgrade is the plan to stay in dracut053 forever ? |
we'll see |
From dracutdevs/dracut#1756 (comment)
I don't think they are going to reverse this decision. After all, it had been deemed probable that Also dracutdevs/dracut#1756 (comment)
It will not be a problem to stick with a downgraded version of I'm not a dev, of course, but I do have a spare system I may lend to experiment with new initramfs generators. Currently, most dev manpower is tied into the gcc/glibc upgrades, thus I guess it'll be a while before a decision is posited. At the very least, let's wait and see what the Gentoo guys will be doing. |
I'll be investigating whether it's practical to switch to another initramfs generator sometime soon, but everything is back to working for now. We've noticed the trend with dracut melding with sysd stuff too and that weighs strongly on decisions about it. at least for now, you can use xbps-alternatives to easily switch to mkinitcpio, booster, or other future initramfs generators |
network-legacy dracut module is supported in dracut v56 and dracut v57. By supported I mean there are tests for NFS, ISCSI, NBD network boot with and without multiple NICs with network-legacy. With v56 dracut you need to be more specific regarding what dracut modules you want in your initramfs.
Dracut latest upstream is specifically tested on openrc (and musl) using a Gentoo container. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
if we switch, it would be to an initramfs generator that's already packaged and well-tested with void. this issue is not for bikeshedding that. |
@abby I think we should consider this issue closed following the reversion to 053. As I noted in #297 (comment), the outstanding issue is not really with this project, but with our failure to identify and patch or remove incompatible modules in the Void |
this doesn't happen in the console images because no network manager. It works fine on dracut 053.
log highlights:
fuller log
The text was updated successfully, but these errors were encountered: