The example 2 in my first posting is not an bug since the package contains /lib/systemd/network/80-container-host0.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/80-container-host0.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 ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1713226 Title: systemd-networkd messes up networking Status in ifupdown package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Since systemd-234-2ubuntu8 systemd-networkd is enabled by default. This causes problems existing configurations ex1: if the network has ipv6 enables (the host recieves a router advertisement), networkmanager does not configure the network anymore so you get only ipv6 and no ipv4 connections (since systemd-networkd seems to bring only the link up) ex2: if you use systemd-nspawn and configured static ip addresses in /etc/network/interfaces, systemd-networkd adds a dhcp obtained address on the host0 adapter and a 169.254 address For the average user both is not expected, so my solution was systemctl disable systemd-networkd, but since you seem to insist having this enabled, it must be made sure systemd-networkd does not touch existing configurations. My suggestion is: 1) if /etc/network/interfaces contains anything other than lo -> do not enable systemd-networkd 2) if network-manager is enabled, systemd-networkd must be disabled and vice versa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1713226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
