Comment #6 is the correct solution. On desktop images we want NM to
manage everything, thus the installer creates
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf. But on a
server, container, or similar environment we do NOT want NM to suddenly
take over existing connections from netplan, networkd, or ifupdown --
there it should be restricted to wifi and 3G.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manager does not manage ethernet and bluetooth interfaces when
Ubuntu 16.10 is installed using chroot/netboot method
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
