[systemd-devel] systemd-networkd: broken network in container

[arnaud gaboury]

On Tue, Nov 22, 2016 at 4:54 PM arnaud gaboury <arnaud.gaboury at gmail.com>
wrote:

> Since a few days, after some upgrades, I don't have anymore network in my
> container. Network is OK on my host
>
> -------------------------------
> Host: Archlinux -
> % systemctl --version
> systemd 231
> +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP
> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
>
> Container: Fedora 24 -
> % systemctl --version
> systemd 229
> +PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
> --------------------------------------
>
> Looking at journalctl on host, I found these errors:
>
> Nov 22 13:47:54 hortensia systemd-networkd[2777]: br0: Could not append
> VLANs: Operation not permitted
> Nov 22 13:47:54 hortensia systemd-networkd[2777]: br0: Failed to assign
> VLANs to bridge port: Operation not permitted
> Nov 22 13:47:54 hortensia systemd-networkd[2777]: br0: Could not set
> bridge vlan: Operation not permitted
> Nov 22 13:47:54 hortensia systemd-networkd[2777]: enp7s0: IPv6 disabled
> for interface: Success
> Nov 22 13:47:55 hortensia systemd-networkd[2777]: enp7s0: Could not append
> VLANs: Operation not permitted
> Nov 22 13:47:55 hortensia systemd-networkd[2777]: enp7s0: Failed to assign
> VLANs to bridge port: Operation not permitted
> Nov 22 13:47:55 hortensia systemd-networkd[2777]: enp7s0: Could not set
> bridge vlan: Operation not permitted
> Nov 22 13:47:55 hortensia systemd[1]: Started Network Service.
> --------------------------------------------------------
>
> Googling these above lines brings me to this issue: #3876[0]
>
> Any progress on it? I can't see where these errors come from. Any hint or
> dirty hack ?
>

EDIT:

This post[1] gave me the answer. Sad it was already post by me a few months
ago ! I just forgot to make permanent the change to the unit file. So when
I upgrade systemd (a few days ago), the wrong setting came back.
Now I edited the unit file and wrote a unitfile.d/override.conf file, so
change will survive next upgrade :-)

Sorry for the noise.

[1]
https://lists.freedesktop.org/archives/systemd-devel/2016-August/037317.html


> [0]https://github.com/systemd/systemd/issues/3876
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20161122/3e4a9d0e/attachment.html>