[amaccuish]

The one I'm currently fighting server-side is netplan. I want to use systemd-networkd directly, since it exposes a lot more features than netplan, but getting netplan to stop intervening is a ballache. Like, it's not a systemd service, it has to be disabled on the kernel command line?!

[jschwartzi]

Yeah I was trying to get systemd-networkd to handle hotplugging, and I spent about a day trying to figure out how to describe a computer with one Ethernet port to netplan before giving up and removing the whole package. At which point systemd-networkd started working beautifully as-expected. For a system administration tool netplan is wonderful at making the simple things needlessly complicated.

[nightfly]

I've found that if you delete /etc/netplan (just making sure this is at least empty seems to be the most important part) and /var/run/systemd/network netplan doesn't really seem to do anything. My org has been using systemd-networkd directly after doing that for about a year and it's working fine for us.

[amaccuish]

Yes I've done that and it definitely works, though I've still got "netcfg/do_not_use_netplan=true" in my cmdline for good measure, not sure if it does anything though, or even when I got that from, come to think of it.

But still, emptying a directory is not how I expect to disable what is a system service. It should be systemctl disable netplan...

I think emptying would be better than deleting the directory since it'll probably just get recreated on an update.

[nightfly]

It's because netplan uses a system generator /lib/systemd/system-generators/netplan, to parse the files in /etc/netplan and generate systemd-networkd configs from them on boot (Like how /etc/fstab gets parse into systemd mount units). It would be nice if there was a flag file or something you could touch to disable it though.