I can confirm this behavior after update to systemd 237-3ubuntu10.39 on privileged and unprivileged containers. We classify this bug as critical because in the next monthly update cycle via ansible orchestration we would expect failing all Bionic LXC containers. The only workaround seems to manually define a static network configuration in /etc/netplan/10-lxc.yaml via lxc-attach. But this is not an acceptable solution for 180 servers we run.
Some our Plesk servers already failed completely due to automatic upgrades Plesk triggered daily. Websites were down for hours until we figured out the reason. I would appreciate that someone solves this problem due to urgency. Thank you in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863873 Title: Systemd fails to configure bridged network in LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
