This was an upstream regression with mounting within user namespaces. It
has been fixed, closing the systemd bug as invalid.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To clarify, this was an upstream *kernel* regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837894
Title:
systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
To manage notifications
Please check 242-2ubuntu1 in eoan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837894
Title:
systemd 240-6ubuntu9 ADT test failure with linux 5.3.0-0.1
To manage notifications about this bug go
We've also seen regressions with lxc which atm appear to be related to a
regression in mounting sysfs in containers which use user namespaces
(bug 1837888 for reference, though there's no activity on the bug as of
yet, just some irc discussion about the regression).
--
You received this bug notif
boot-and-services failed because:
Jul 24 13:09:02 autopkgtest systemd[1]: Starting Container c1...
Jul 24 13:09:02 autopkgtest systemd-nspawn[891]: Failed to mount sysfs (type
sysfs) on /sys/full (MS_RDONLY|MS_NOSUID|MS_NODEV|MS_NOEXEC ""): Operation not
permitted
Jul 24 13:09:02 autopkgtest syst
