Systemd: networkd core dumped after a docker container is finished

[xabbu]

systemd version the issue has been seen with

240

Used distribution

Arch Linux

Unexpected behaviour you saw

systemd-networkd core dumped after a docker container is finished. It started with systemd 240.0-3 and is still present in 240.34-2. networkd restarts after the core dump. The docker version is 18.09.1.
It happens with containers which stops very quickly after the start. The container form the log below ran around 3 seconds until it was finished. I did not see this problem with long running container.
The networkd error message is

Assertion 'link->manager' failed at ../systemd-stable/src/network/networkd-link.c:3079, function link_initialized_and_synced(). Aborting

A more complete journal extract

Jan 13 11:05:00 xabbu.me kernel: docker0: port 3(veth68de3cc) entered blocking state
Jan 13 11:05:00 xabbu.me kernel: docker0: port 3(veth68de3cc) entered disabled state
Jan 13 11:05:00 xabbu.me kernel: device veth68de3cc entered promiscuous mode
Jan 13 11:05:00 xabbu.me kernel: IPv6: ADDRCONF(NETDEV_UP): veth68de3cc: link is not ready
Jan 13 11:05:00 xabbu.me systemd-udevd[20838]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 13 11:05:00 xabbu.me systemd-udevd[20838]: Could not generate persistent MAC address for veth2aeef64: No such file or directory
Jan 13 11:05:00 xabbu.me systemd-udevd[20839]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 13 11:05:00 xabbu.me systemd-udevd[20839]: Could not generate persistent MAC address for veth68de3cc: No such file or directory
Jan 13 11:05:00 xabbu.me kernel: eth0: renamed from veth2aeef64
Jan 13 11:05:00 xabbu.me systemd-networkd[19838]: veth68de3cc: Gained carrier
Jan 13 11:05:00 xabbu.me kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth68de3cc: link becomes ready
Jan 13 11:05:00 xabbu.me kernel: docker0: port 3(veth68de3cc) entered blocking state
Jan 13 11:05:00 xabbu.me kernel: docker0: port 3(veth68de3cc) entered forwarding state
Jan 13 11:05:02 xabbu.me systemd-networkd[19838]: veth68de3cc: Gained IPv6LL
Jan 13 11:05:03 xabbu.me systemd-networkd[19838]: veth68de3cc: Lost carrier
Jan 13 11:05:03 xabbu.me kernel: docker0: port 3(veth68de3cc) entered disabled state
Jan 13 11:05:03 xabbu.me systemd-udevd[20838]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 13 11:05:03 xabbu.me kernel: docker0: port 3(veth68de3cc) entered disabled state
Jan 13 11:05:03 xabbu.me kernel: device veth68de3cc left promiscuous mode
Jan 13 11:05:03 xabbu.me kernel: docker0: port 3(veth68de3cc) entered disabled state
Jan 13 11:05:04 xabbu.me systemd-networkd[19838]: Assertion 'link->manager' failed at ../systemd-stable/src/network/networkd-link.c:3079, function link_initialized_and_synced(). Aborting.
Jan 13 11:05:04 xabbu.me systemd[1]: Started Process Core Dump (PID 21152/UID 0).
Jan 13 11:05:04 xabbu.me systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT
Jan 13 11:05:04 xabbu.me systemd[1]: systemd-networkd.service: Failed with result 'core-dump'.
Jan 13 11:05:04 xabbu.me systemd[1]: systemd-networkd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Jan 13 11:05:04 xabbu.me systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 11.
Jan 13 11:05:04 xabbu.me systemd[1]: systemd-networkd-wait-online.service: Succeeded.
Jan 13 11:05:04 xabbu.me systemd[1]: Stopped Wait for Network to be Configured.
Jan 13 11:05:04 xabbu.me systemd[1]: Stopping Wait for Network to be Configured...
Jan 13 11:05:04 xabbu.me systemd[1]: Stopped Network Service.
Jan 13 11:05:04 xabbu.me systemd[1]: Starting Network Service...
Jan 13 11:05:04 xabbu.me systemd-coredump[21153]: Process 19838 (systemd-network) of user 981 dumped core.

                                                  Stack trace of thread 19838:
                                                  #0  0x00007fe767e6cd7f raise (libc.so.6)
                                                  #1  0x00007fe767e57672 abort (libc.so.6)
                                                  #2  0x00007fe767bf202c n/a (libsystemd-shared-240.so)
                                                  #3  0x00005612a1ac49e2 n/a (systemd-networkd)
                                                  #4  0x00005612a1ac61ec n/a (systemd-networkd)
                                                  #5  0x00007fe767c2f4d7 sd_netlink_process (libsystemd-shared-240.so)
                                                  #6  0x00007fe767c2f7d4 n/a (libsystemd-shared-240.so)
                                                  #7  0x00007fe767c22220 n/a (libsystemd-shared-240.so)
                                                  #8  0x00007fe767c22511 sd_event_dispatch (libsystemd-shared-240.so)
                                                  #9  0x00007fe767c226d9 sd_event_run (libsystemd-shared-240.so)
                                                  #10 0x00007fe767c228fc sd_event_loop (libsystemd-shared-240.so)
                                                  #11 0x00005612a1a9b288 n/a (systemd-networkd)
                                                  #12 0x00007fe767e59223 __libc_start_main (libc.so.6)
                                                  #13 0x00005612a1a9be2e n/a (systemd-networkd)
Jan 13 11:05:04 xabbu.me systemd[1]: [email protected]: Succeeded.
Jan 13 11:05:05 xabbu.me systemd-networkd[21170]: docker0: Gained IPv6LL
Jan 13 11:05:05 xabbu.me systemd-networkd[21170]: eth0: Gained IPv6LL
Jan 13 11:05:05 xabbu.me systemd-networkd[21170]: Enumeration completed
Jan 13 11:05:05 xabbu.me systemd[1]: Started Network Service.

[yuwata]

Thanks. Could you test PR #11412?

[xabbu]

I rebuilt the arch systemd 240.34-2 package with your PR #11412 . The system runs now around 3 h without any systemd-networkd core dump.
It looks like this PR fixes the problem.

[yuwata]

Thank you for testing.