You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of removing files from installed packages, wouldn't it be possible to split the systemd package in two, and just not install systemd-networkd, so it would be possible to layer systemd-networkd manually after.
The text was updated successfully, but these errors were encountered:
mildred
changed the title
networkd cannot be used in CoreOS
systemd-networkd cannot be used in CoreOS
Nov 29, 2019
Instead of removing files from installed packages, wouldn't it be possible to split the systemd package in two, and just not install systemd-networkd, so it would be possible to layer systemd-networkd manually after.
Yeah, that'd probably work, though note this isn't just about users' choices. There's code that runs on top that need to understand the networking stack and interact with it (see e.g. coreos/afterburn#316). So supporting systemd-networkd would also mean having to support it in those apps too.
If you don't mind, I think I'd rather close this issue so we keep the discussion in that ticket. Thanks!
I'd prefer to use systemd-networkd instead of Networkmanager in a server setup.
This is made impossible by:
fedora-coreos-config/manifests/fedora-coreos-base.yaml
Lines 49 to 55 in 54817dd
Instead of removing files from installed packages, wouldn't it be possible to split the systemd package in two, and just not install systemd-networkd, so it would be possible to layer systemd-networkd manually after.
The text was updated successfully, but these errors were encountered: