> Right so the bug her eis that your session-c2.scope was created without giving you ownership of the directory
Indeed this hasn't previously been done for the "systemd" controller; it didn't seem necessary with previous LXC versions, but apparently is now. Chowning the
> and the tasks and cgroup.procs files.
No, I am not going to own those to the user. This would be a (small) privilege escalation bug, as the user could then move processes from a less privileged session (like from ssh) to a more privileged one (like a local desktop session). This also doesn't seem to be necessary, neither for upstart nor systemd containers.
> Right so the bug her eis that your session-c2.scope was created without giving you ownership of the directory
Indeed this hasn't previously been done for the "systemd" controller; it didn't seem necessary with previous LXC versions, but apparently is now. Chowning the
> and the tasks and cgroup.procs files.
No, I am not going to own those to the user. This would be a (small) privilege escalation bug, as the user could then move processes from a less privileged session (like from ssh) to a more privileged one (like a local desktop session). This also doesn't seem to be necessary, neither for upstart nor systemd containers.