please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1732411
Title:
On
A fix [1] in LXC was pushed recently and actually allows systemd daemon-
reexec without the cap sys_admin in a container.
We tested that it totally solved the issue for us.
Would it possible to move this bug report to the LXC project? And to ask for a
backport of such fix to Xenial LXC?
Thanks!
Could you describe the minimal steps to reproduce the issue on top of a
standard 16.04?
NB: /sys is not read-only on official images and deployments, and this
doesn't seem to affect official images.
** Description changed:
Dear all,
- Following up the bug report #1713674, when executing
>From our analysis, we indeed agree with the fact that it has nothing to do
>with LXC (hence the report in the systemd tracker).
We believe that only the package is faulty here and should not attempt to
blindly reexec systemd on upgrade.
--
You received this bug notification because you are a
Marking the lxc task as invalid since LXC does not drop any such
capabilities by default, so such failure isn't lxc's fault. It's either
the user's fault (by dropping capabilities that Ubuntu/Debian consider
as required) or the systemd's package fault (for not doing a capability
check).
**
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1732411
Title:
On upgrade, daemon-reexec should
6 matches
Mail list logo