Arch Linux

Toolybird

Member

Registered: 2017-09-30

Posts: 72

systemd-238.51 causing trouble with nspawn containers autostart

Upon reboot some of my autostarting nspawn containers refuse to start:

Failed to add new veth interfaces (vb-plex:host0): File exists

Seems like some kind of race condition.

This looks similar:

https://github.com/systemd/systemd/issues/2173

Downgrading to systemd-238.0-3 immediately resolves problem.

Anyone else?

johnpc

Member

Registered: 2018-03-28

Posts: 2

Re: systemd-238.51 causing trouble with nspawn containers autostart

I can confirm. Updated the host and 1 guest. The older container running 238.0-3 now shows this:

Mar 28 16:23:15 host systemd-nspawn[32065]: Failed to add new veth interfaces (ve-guestname:host0): File exists

While the updated container never even creates the virtual interface. Downgrading the host resolved both issues (guest can still run 238.51).

The systemd-nspawn@.service override I use is

$ cat /etc/systemd/system/systemd-nspawn@.service.d/override.conf
[Service]
ExecStart=
ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth --settings=trusted --machine=%I

Toolybird

Member

Registered: 2017-09-30

Posts: 72

Re: systemd-238.51 causing trouble with nspawn containers autostart

Acknowledged as a regression upstream:

https://github.com/systemd/systemd/issues/8599

johnpc

Member

Registered: 2018-03-28

Posts: 2

Re: systemd-238.51 causing trouble with nspawn containers autostart

This issue resolved for me after updating all containers and host to 238.51 and rebooting.

Toolybird

Member

Registered: 2017-09-30

Posts: 72

Re: systemd-238.51 causing trouble with nspawn containers autostart

A fix has been merged upstream:

https://github.com/systemd/systemd/pull/8633