--
You received this message because you are subscribed to the Google Groups "lxc-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lxc-users+...@lists.linuxcontainers.org.
To view this discussion on the web visit https://groups.google.com/a/lists.linuxcontainers.org/d/msgid/lxc-users/da70a9bb-2bcf-4e57-ba53-5e60593892den%40lists.linuxcontainers.org.
Probably shouldn't get too used to netplan either.
Within the space of a few short years we've seen ifupdown, network manager, and netplan, which I'm guessing will soon be replaced by systemd-network.service
On Wed, Jun 30, 2021 at 1:38 PM Brian Candler <b.ca...@pobox.com> wrote:Bridges are a perfectly good way to have multiple containers share one network interface. I use lxd with netplan and bridges (and presumably lxc would be fine as well).There is no need to install ifupdown: it was only a transition mechanism for Ubuntu 16.04->18.04 and may not be available at all in 20.04. You should get used to it now.
Since the current Ubuntu uses netplan, every time I need to deploy my LXC containers, I need to remove netplan and install ifupdown, but that always requires KVM access because you will get kicked out.
What would it be the "legal" way to deploy many containers sharing a single network interface, under netplan, considering the bridges are not the preferred option because of performance. I have failed to find one.