FS#58382 - [systemd] Cannot run multiple unprivileged systemd-nspawn containers simultaneously (upstream #8599)
Attached to Project:
Arch Linux
Opened by Milan (PetaByteBoy) - Saturday, 28 April 2018, 17:34 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 April 2018, 18:00 GMT
Opened by Milan (PetaByteBoy) - Saturday, 28 April 2018, 17:34 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 April 2018, 18:00 GMT
|
Details
Description:
A detailed bug report is available on the upstream issue tracker: https://github.com/systemd/systemd/issues/8599 Additional info: The regression was introduced in a fix. This fix was backported to v238-stable: https://github.com/systemd/systemd-stable/commit/649030e8cb00b2a9f1767cb8f77f7edb522b1dfb A fix for the regression was commited to master 23 days ago as of writing this: https://github.com/systemd/systemd/commit/7511655807e90aa33ea7b71991401a79ec36bb41 But upstream does not seem to be willing to backport the fix to v238-stable. I suggest including the fix as a patch in the ArchLinux package until systemd v239. Steps to reproduce: See the detailed bug report at https://github.com/systemd/systemd/issues/8599 |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 28 April 2018, 18:00 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#58088
Saturday, 28 April 2018, 18:00 GMT
Reason for closing: Duplicate
Additional comments about closing:
FS#58088?I did have the issue after the 10th, but maybe my system was not up to date. In case I can reproduce it with the latest package I'll request a reopen on #58088.