Yeah, it's pretty much an implementation detail - the thing running your containers likely exposes knobs like 'memory limit' and 'cpu limit' and under the hood

Yeah, it's pretty much an implementation detail - the thing running your containers likely exposes knobs like 'memory limit' and 'cpu limit' and under the hood it takes care of manipulating the files within the mounted cgroup filesystem. You'll be pleased that at least with cgroups v2 there's only a single /sys/fs/cgroup instead of half a dozen filesystems mounted underneath that path. :)