Description of problem: This is a regression documented in https://github.com/systemd/systemd/issues/8599 . Please consider include backports into fedora 28. Without that systemd-nspawn cannot be used with private users and private networking. How reproducible: 100% Steps to Reproduce: 1. dnf install debootstrap 2. debootstrap unstable /var/lib/machines/debian-tree 3. systemd-nspawn -n -U -D /var/lib/machines/debian-tree 4. ip link show # this runs in the container Actual results: Only lo device is shown in the container Expected results: Both lo and a device like host0@if39 should be shown in the container.
Host interfaces (container is m1): ----------------- 51: host0@ve-m1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 32:db:72:93:f3:3d brd ff:ff:ff:ff:ff:ff 52: ve-m1@host0: <NO-CARRIER,BROADCAST,MULTICAST,UP,M-DOWN> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000 link/ether 0e:89:bb:fe:8a:60 brd ff:ff:ff:ff:ff:ff Container Interfaces: ----------------------- 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever
Created attachment 1475640 [details] Backported - 751165580 nspawn: wait for network namespace creation before interface setup (#8633) Backported the indicated upstream patch and the problem is no longer observed.
Good afternoon, Looking at the latest version released, it looks like the necessary patch is included. Specifically, this one: https://github.com/systemd/systemd-stable/commit/7511655807e90aa33ea7b71991401a79ec36bb41 ~~~ nspawn: wait for network namespace creation before interface setup (#… …8633) Otherwise, network interfaces can be "moved" into the container's namespace while it's still the same as the host namespace, in which case e.g. host0 for a veth ends up on the host side instead of inside the container. Regression introduced in 0441378. Fixes #8599. ~~~ Can you confirm that systemd-238-10.git438ac26.fc28 resolves the issue? - Kyle Walker
In F29 the problem is solved. I cannot tell about F28 as I upgraded my system.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.