Control: reassign -1 lxc
On Wed, 16 Jan 2019 09:52:47 +0100 Matthijs Kooijman
wrote:
> severity 919259 normal
> found 919259 232-25
> retitle 919259 Reexecuting fails in containers without CAP_SYS_ADMIN
> thanks
>
> Hey Michael,
>
> > My suggestion would be to roll back to 232-25+deb9u1 and the
Processing control commands:
> reassign -1 lxc
Bug #919259 [systemd] Reexecuting fails in containers without CAP_SYS_ADMIN
Bug reassigned from package 'systemd' to 'lxc'.
No longer marked as found in versions systemd/232-25 and systemd/232-25+deb9u7.
Ignoring request to alter fixed versions of bug
Processing commands for cont...@bugs.debian.org:
> severity 919259 normal
Bug #919259 [systemd] systemd: (Security?) update breaks systemd (inside
unprivileged container?)
Severity set to 'normal' from 'important'
> found 919259 232-25
Bug #919259 [systemd] systemd: (Security?) update breaks syst
severity 919259 normal
found 919259 232-25
retitle 919259 Reexecuting fails in containers without CAP_SYS_ADMIN
thanks
Hey Michael,
> My suggestion would be to roll back to 232-25+deb9u1 and then gradually
> upgrading to deb9u2, deb9u2 ... deb9u3
Yeah, that was my intention. I discovered some int
Am 14.01.19 um 08:22 schrieb matthijs:
> I looked through the changelog from deb9u1 to deb9u7, and nothing springs out
> as an obvious cause. Only the last update was a security update (relating to
> the journal only), so this might be caused by one of the previous non-security
> updates as well (w
Package: systemd
Version: 232-25+deb9u7
Severity: important
Hi folks,
this morning, some lxc containers on my machine did an unattended upgrade from
systemd 232-25+deb9u1 to version 232-25+deb9u7. As part of that upgrade,
systemd was reexecuted, which resulted in systemd freezing:
systemd[1]: Re
