Bug#1076728: elogind: privileged operation with polkit fails

[Andrew Bower]

On Wed, Dec 18, 2024 at 07:01:35PM +0000, Mark Hindley wrote:
> Control: retitle -1 elogind: use of cgroups conflicts with docker.io
> 
> On Wed, Dec 18, 2024 at 06:29:32PM +0000, Andrew Bower wrote:
> > Control: tags 1076728 - moreinfo unreproducible
> > 
> > Hi Mark,
> > 
> > On Wed, Dec 18, 2024 at 10:10:03AM +0000, Mark Hindley wrote:
> > > Can you please check the runtime data?
> > > 
> > > How is /sys/fs/cgroup mounted?
> > 
> > Differently from yours...
> 
> I am pleased we have found something
> 
> Lorenzo, you reported this originally. Can you confirm you have docker.io
> installed and it is the same issue?

Worth noting that:

1) The docker initscript wants cgroupfs-mount to have been started first.
   This is not present on my system. Maybe we end up with a different
   layout depending on whether this is present.

   If I start to install cgroupfs-mount I get alerted to:

   serious bugs of cgroupfs-mount (→ 1.4+nmu1) <Outstanding>
    b1 - #1070295 - cgroupfs-mount: Fails to upgrade or remove if elogind is running: "umount: /sys/fs/cgroup/elogind: target is busy."

2) Lorenzo recently added a docker service to runit-services that
   follows the same runes as the docker initscript, minus the
   attempt to start cgroupfs-mount first.

> > I think we can therefore move this bug to docker.io?
> 
> Maybe. I am at (or probably beyond) my area of expertise. At the moment I am
> unsure if elogind ought to be using its own cgroups namespace or if docker.io is
> behaving badly here. Time for some reading....

None of this is within my area of competence!