[systemd-devel] network config breaks when starting a nspawn container

[Francis Moreau]

On Thu, Jan 27, 2022 at 7:26 AM Francis Moreau <francis.moro at gmail.com> wrote:
>
> Hi,
>
> systemd-networkd creates a bridge 'br0':
>
> $ cat /etc/systemd/network/30-br0.network
> [Match]
> Name=br0
>
> [Network]
> DHCP=ipv4
> Domains=~.
>
> The bridge has one slave 'bond0' by default. The bond device is used
> to
> aggregate my ethernet card and my wifi card (configured by NM).
>
> systemd-resolved is also used.
>
> Every thing works until I start a container 'c1' which should connect
> to br0:
>

Interestingly this only happens when the active interface in the bond
device is the wifi interface.