FS#59155 - [systemd] systemd-networkd 239.0-2 failing inside lxc unpriviliged container

Attached to Project: Arch Linux
Opened by ipp (n8V8r) - Wednesday, 27 June 2018, 09:31 GMT
Last edited by Christian Hesse (eworm) - Thursday, 05 July 2018, 19:20 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

netwrokd 238 working but after installing 239 producing:

systemd[58]: systemd-networkd.service: Failed to update dynamic user credentials: Permission denied
systemd[58]: systemd-networkd.service: Failed at step USER spawning /usr/lib/systemd/systemd-networkd: Permission denied
systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=217/USER
systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
systemd[1]: systemd-networkd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 4.
systemd[1]: systemd-networkd.service: Failed to reset devices.list: Operation not permitted
systemd[63]: systemd-networkd.service: Failed to update dynamic user credentials: Permission denied
systemd[63]: systemd-networkd.service: Failed at step USER spawning /usr/lib/systemd/systemd-networkd: Permission denied
systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=217/USER
systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
systemd[1]: systemd-networkd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
systemd[1]: systemd-networkd.service: Scheduled restart job, restart counter is at 5.
systemd[1]: systemd-networkd.service: Start request repeated too quickly.
systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
systemd[1]: systemd-networkd.socket: Failed with result 'service-start-limit-hit'.

Additional info:
* host ubuntu 4.15.0-23 (being a VPS on a KVM hypervisor with virtio driver)
* unpriviliged lxc container archlinux
* lxc 3.0.1


Steps to reproduce:
* install lxc on host
* create/configure unpriviliged lxc container with archlinux as guest
* start unprivilged lxc container
* login to unprivilged lxc container
* pacman -Syu
* pacman -S wget
* wget https://ind.mirror.pkgbuild.com/testing/os/x86_64/systemd-239.0-2-x86_64.pkg.tar.xz
* pacman -U systemd-239.0-2-x86_64.pkg.tar.xz
* installation succeeds with no error report
* reboot the unprivilged lxc container and the errors cited above are present
This task depends upon

Closed by  Christian Hesse (eworm)
Thursday, 05 July 2018, 19:20 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Not a bug, at least not a systemd one.
Comment by ipp (n8V8r) - Wednesday, 27 June 2018, 14:15 GMT
This been discussed also at upstream https://github.com/systemd/systemd/issues/9427
Comment by Christian Hesse (eworm) - Wednesday, 27 June 2018, 14:17 GMT
Caused by systemd using DynamicUser for systemd-networkd now:

https://github.com/systemd/systemd/issues/9427
Comment by ipp (n8V8r) - Thursday, 28 June 2018, 10:15 GMT
Moved onto another distro with other networking tools than |networkd|, hence please feel at libery to close the task.
Comment by Christian Hesse (eworm) - Monday, 02 July 2018, 06:29 GMT
Wondering if this is an issue of the host system... Does anybody run arch containers on another lxc host system?
Comment by Christian Hesse (eworm) - Tuesday, 03 July 2018, 15:31 GMT
After #9427 was closed I opened a new upstream issue:
https://github.com/systemd/systemd/issues/9493

Feel free to comment if you have any details.
Comment by Christian Hesse (eworm) - Thursday, 05 July 2018, 19:18 GMT
Looks like this is an issue with Linux and Apparmor on the host system, see the upstream report for details.
As we can not wait for all distributions to publish fixes packages I will close this bug now and move systemd v239 to [core].

In case you need to fix sysetemd-networkd: Create a file /etc/systemd/system/systemd-networkd.service.d/override.conf with this content:

[Service]
DynamicUser=no

Loading...