Yeah, systemd 244.1 is causing this issue because of a change of detection of container logic within systemd.
There may be some way to put a systemd override around systemd-networkd to have that service run in a mount namespace that serves /sys read-only, this would cause systemd to revert to the old working behavior. The long term fix is a kernel change so that udevd can behave properly such that networkd also behaves as expected. We're looking into this now but it will take some time before that's ready. On Wed, Jan 1, 2020 at 10:36 AM John <l...@jelmail.com> wrote: > Hello, > > Just reporting this problem I'm experiencing with Arch Linux on LXD. > > Create container using "images:archlinux/current/amd64" and with a > network interface connected to a bridge. > > Configure /etc/systemd/network/mynetif.network to configure by DHCP: > > [Match] > Name=mynetif > > [Network] > DHCP=ipv4 > > Start network > > # systemctl enable --now systemd-networkd > > Observe network stuck pending > > # networkctl > IDX LINK TYPE OPERATIONAL SETUP > 1 lo loopback carrier unmanaged > 335 mynetif ether routable pending > > Confirm systemd version > > # systemctl --version > > systemd 244 (244.1-1-arch) > +PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP > +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS > +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid > > Install systemd 243.78.2-arch > (download from https://archive.archlinux.org/packages/s/systemd) > > (from outside container) > # lxc file push systemd-243.78-2-x86_64.pkg.tar.xz mycontainer/root > > (then inside container) > # pacman -U systemd-243.78-2-x86_64.pkg.tar.xz > > Confirm systemd version > > # systemctl --version > systemd 243 (243.78-2-arch) > +PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP > +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS > +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid > > Restart systemd-networkd > > # systemctl restart systemd-networkd > > Observer network configured successfully > > # networkctl > > IDX LINK TYPE OPERATIONAL SETUP > 1 lo loopback carrier unmanaged > 335 mynetif ether routable configured > > I did look at the system-networkd journal and there was nothing there to > indicate a problem. If I manually configure the interface (using ip) > then it works (so the network layer is ok, it's just systemd starting > things that's broken). > > Anyone else observe this? > _______________________________________________ > lxc-users mailing list > lxc-users@lists.linuxcontainers.org > http://lists.linuxcontainers.org/listinfo/lxc-users > -- Stéphane
_______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users
