Re: host0 virtual link suddenly default down in systemd-nspawn container

[Ansgar Burchardt <ansgar@xxxxxxxx>]

Johannes Ernst writes:
> I've been running the same systemd-nspawn container for some time, always with the same options:
>
> 	systemd-nspawn -b -n -D dir -M name --bind /home -x
>
> It would always bring up the virtual ethernet link immediately during
> boot of the container. But since a recent Arch (host) upgrade (I
> think), the virtual ethernet link host0 now stays "down" during boot
> of the container:

Do you use systemd-networkd?  I noticed that systemd-networks no longer
starts in nspawn containers (the condition for CAP_NET_ADMIN failed), so
nothing configured the network interface after upgrading to systemd 243
in Debian experimental.

I haven't had time to investigate the problem further.

Ansgar
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel