Philipp Wendler

There is a nice overview of the current state and information about cgroup-v2 in these [slides](http://man7.org/conf/meetup/conf_cgroups_v2--jambit-Kerrisk-2019-06-05.pdf). It claims that `cpuset` and `cpu` were added, but `freezer` is still missing.

We do not need `freezer` in container mode, so we can really start implementing support for cgroup v2 now. Suggested order of steps: - Implement #173 (we need a separate...

Nothing has happened since then due to lack of manpower and because AFAIK most distributions still use hybrid mode with all controllers in cgroups-v1 hierarchies by default anyway. But of...

Yes, a v2 version will absolutely exist, there was never any question about it. Since recently we have someone working on this.

@globin is actively working on this and the ETA is some time in the next weeks or (few) months. I am surprised to hear that Docker should have problems with...

A heads-up warning for everyone waiting on cgroups-v2: While implementing this in BenchExec, we noticed that the kernel does not provide the required memory measurements with cgroups-v2. The [list of...

To anyone waiting for this: We have a draft PR for cgroupsv2 support (#791) and basic functionality is working. You are invited to test this and we welcome feedback in...

Yes. `memory.peak` is a really recent feature from Linux 5.19 and newer than the comment that you quoted. :-) We will add support for it, but because it is so...

This could be not just a binary choice, we could have possible values like `fail` (makes BenchExec fail if pattern does not match), `warn` (current behavior), `ignore` (avoid warning), and...

This could be added, but is quite low priority for me.