FS#58111 - [systemd] machinectl start won't boot up a container with --network-veth flag

Attached to Project: Arch Linux
Opened by Christian Rebischke (Shibumi) - Wednesday, 04 April 2018, 21:20 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 05 April 2018, 15:56 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

the machinectl start <containername> should boot up a container according to the systemd-nspawn@.service file with the following parameters:

# systemctl cat systemd-nspawn@.service
[..]
ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth -U --settings=override --machine=%i
[..]

There is definitly the `--network-veth`-parameter. But when i start the container with `machinectl start <containername>` I can't see any ve-interface in the container itself. Outside there are two interfaces:

17: host0@ve-archlinux: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 6a:2c:0d:b0:b9:40 brd ff:ff:ff:ff:ff:ff
18: ve-archlinux@host0: <NO-CARRIER,BROADCAST,MULTICAST,UP,M-DOWN> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000
link/ether 52:0e:53:b3:3b:f6 brd ff:ff:ff:ff:ff:ff



When you start the container like this:

sudo systemd-nspawn -n -D /var/lib/machines/archlinux

the network-interfaces are there.

Version: systemd 238
+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN +PCRE2 default-hierarchy=hybrid
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 05 April 2018, 15:56 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#58088 
Comment by Christian Rebischke (Shibumi) - Wednesday, 04 April 2018, 21:23 GMT
Steps to reproduce this issue:

pacstrap a container with: pacstrap -c -d "/var/lib/machines/archlinux" base openssh
start it with: machinectl start work
login with: machinectl login work and check the interfaces
OR
login with: machinectl shell archlinux
Comment by Christian Rebischke (Shibumi) - Wednesday, 04 April 2018, 21:27 GMT
This seems to have to do with: https://github.com/systemd/systemd/issues/8649
Comment by Christian Rebischke (Shibumi) - Wednesday, 04 April 2018, 21:27 GMT
Might be a duplicate with: https://github.com/systemd/systemd/issues/8599
Comment by loqs (loqs) - Wednesday, 04 April 2018, 21:41 GMT
Does the suggested fix https://github.com/systemd/systemd/commit/15cf05375fbe6419321550969015e298b77a4456 work for you?

Loading...