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:
[container]# ip addr
...
2: host0@if16: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
group default qlen 1000
link/ether c6:20:a3:f7:c4:3c brd ff:ff:ff:ff:ff:ff link-netnsid 0
I can manually bring it up, and then all is well:
[container]# ip link set host0 up
[container]# ip addr
...
2: host0@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether c6:20:a3:f7:c4:3c brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.75.70/28 brd 192.168.75.79 scope global dynamic host0
valid_lft 3598sec preferred_lft 3598sec
inet6 fe80::c420:a3ff:fef7:c43c/64 scope link
valid_lft forever preferred_lft forever
I’m using the default host0.network from
https://github.com/systemd/systemd/blob/master/network/80-container-host0.network
How do I get it back to default-up? And what may have happened to cause this
change in behavior, because the container itself did not change.
Thanks,
Johannes.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
