Re: [systemd-devel] name=systemd cgroup mounts/hierarchy

2020-11-16 Thread Andrei Enshin
Lennart, > the systemd cgroupfs hierarchy is private property of systemd, and container > managers are supposed to follow this logic if they want to interfere with > this: https://systemd.io/CGROUP_DELEGATION/ I see. Thank you for the link. I’ve also read the https://systemd.io/CONTAINER_IN

Re: [systemd-devel] systemd.automount issue: Failed to initialize automounter: Operation not permitted

2020-11-16 Thread Mantas Mikulėnas
Automounts themselves are established by a magic kernel-level mount (specifically they're "autofs" mounts), which requires root privileges. Your systemd --user instance runs unprivileged, as your own UID, and doesn't have the privilege to mount autofs (or anything else that isn't FUSE). On Tue, N

Re: [systemd-devel] name=systemd cgroup mounts/hierarchy

2020-11-16 Thread Andrei Enshin
Lennart, > the systemd cgroupfs hierarchy is private property of systemd, and container > managers are supposed to follow this logic if they want to interfere with > this: https://systemd.io/CGROUP_DELEGATION/ I see. Thank you for the link. I’ve also read the https://systemd.io/CONTAINER_IN

Re: [systemd-devel] name=systemd cgroup mounts/hierarchy

2020-11-16 Thread Andrei Enshin
Michal, > What exact problem do you see? I see the kubelet crash with error: «Failed to start ContainerManager failed to initialize top level QOS containers: root container [kubepods] doesn't exist» details: https://github.com/kubernetes/kubernetes/issues/95488 > What was 'self'? ‘self’ was a

[systemd-devel] systemd.automount issue: Failed to initialize automounter: Operation not permitted

2020-11-16 Thread Wolter HV
Hello, I'm trying to mount an sshfs share using systemd only, on a user level. Unfortunately, I get the following error message on journalctl: Failed to initialize automounter: Operation not permitted I get that error message on journalctl after I try to start my automount via the c

Re: [systemd-devel] Journald retaining logs for only 10 days

2020-11-16 Thread Andrei Borzenkov
14.11.2020 22:18, Nikolaus Rath пишет: > On Nov 14 2020, Andrei Borzenkov wrote: >> 14.11.2020 14:32, Nikolaus Rath пишет: >> ... > > # grep -vE '^#' /etc/systemd/journald.conf > > [Journal] > SystemMaxUse=300M The number shown by disk usage (320 MB) is higher than 30

Re: [systemd-devel] Antw: [EXT] Re: Journald retaining logs for only 10 days

2020-11-16 Thread Vito Caputo
On Mon, Nov 16, 2020 at 07:43:27AM +, mikko.rap...@bmw.de wrote: > Hi, > > Interesting dicussion, here is one more view point. Few months back we tried > to > limit systemd journald output to retain a few MB of logs on embedded, > headless boxes on a tiny read-write partition in case somethin

[systemd-devel] Antw: Antw: [EXT] Re: Journald retaining logs for only 10 days

2020-11-16 Thread Ulrich Windl
>>> "Ulrich Windl" schrieb am 16.11.2020 um 08:18 in Nachricht <5fb227c402a10003c...@gwsmtp.uni-regensburg.de>: Vito Caputo schrieb am 14.11.2020 um 21:29 in > Nachricht > <20201114202930.x7wbx4p37bkkw...@shells.gnugeneration.com>: >> On Sat, Nov 14, 2020 at 09:31:23AM +, Nikolaus Ra