Comment 7 for bug 1713226

msaxl (saxl) wrote :

The example 2 in my first posting is not an bug since the package contains /lib/systemd/network/ As I wrote this only affects systemd-nspawn containers

the unexpected "thing" is that when you upgrade you do not expect a system wide configuration that is active in parallel to the "old" ifupdown configuration. To keep your old configuration someone can for example touch /etc/systemd/network/

I have no idea how to deal with that "problem", but I think that not many have such configurations and less do a container upgrade instead of a clean update. With luck the rest will be directed here by google ;)