On 7/23/20 12:54 PM, Pavel Tikhomirov wrote:
> We've faced a problem with docker/containerd cgroups configuration code.
> It does write 1(-1) to memory.kmem.limit_in_bytes of newly created
>
> memory cgroup as a verification check that memory cgroup works (we've
> already made a pull request to
We've faced a problem with docker/containerd cgroups configuration code.
It does write 1(-1) to memory.kmem.limit_in_bytes of newly created
memory cgroup as a verification check that memory cgroup works (we've
already made a pull request to containerd to remove this strange check).
We have a fake c