3 ms·

>having all cgroup operations flow through its opinionated dbus api was simply unacceptable for docker, kubernetes, lxc, runc, and everybody else maintaining qu

>having all cgroup operations flow through its opinionated dbus api was simply unacceptable for docker, kubernetes, lxc, runc, and everybody else maintaining quality container runtimes. I think you're off-base on this. Work is being done to get support for cgroupsv2 in all the major container runtimes. Source: https://medium.com/nttlabs/cgroup-v2-596d035be4d7 https://medium.com/nttlabs/cgroup-v2-596d035be4d7 In any case single-writer was not an explicit goal of systemd, it was an intentional design decision that came from the kernel. TFA even mentions this, although it is somewhat lost within the pages of ranting. You also don't even have to use systemd's D-Bus APIs to deal with this. Container managers can if they want to provide additional integrations. Source: https://systemd.io/CGROUP_DELEGATION/ https://systemd.io/CGROUP_DELEGATION/

CameronNemo 6y ago
>Work is being done to get support for cgroupsv2 in all the major container runtimes. That work is done for LXC. It does not go through systemd's dbus api.
- cycloptic 6y ago
  Yes, that was the point of my second paragraph. It doesn't have to. The systemd d-bus api is only if you want your containers to show up in systemd as well. From the perspective of a container manager, all you have is your own little hierarchy sitting somewhere in the tree, the parent leaf is not particularly important. This distinction is relevant for ANY combination of container managers under cgroupsv2, for example if you try to run it multiple levels deep (systemd within an lxc container within a docker container or something like that). The situation with LXC is basically the same anyway. You just dump your containers in a sub-hierarchy and if you decide you want to integrate further with that, you have to use liblxc. It's funny that systemd still for some reason gets these long rants directed at it though.

CameronNemo 6y ago

>Work is being done to get support for cgroupsv2 in all the major container runtimes. That work is done for LXC. It does not go through systemd's dbus api.

cycloptic 6y ago
Yes, that was the point of my second paragraph. It doesn't have to. The systemd d-bus api is only if you want your containers to show up in systemd as well. From the perspective of a container manager, all you have is your own little hierarchy sitting somewhere in the tree, the parent leaf is not particularly important. This distinction is relevant for ANY combination of container managers under cgroupsv2, for example if you try to run it multiple levels deep (systemd within an lxc container within a docker container or something like that). The situation with LXC is basically the same anyway. You just dump your containers in a sub-hierarchy and if you decide you want to integrate further with that, you have to use liblxc. It's funny that systemd still for some reason gets these long rants directed at it though.