11:pids:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
10:perf_event:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
9:memory:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
8:blkio:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
7:hugetlb:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
6:cpuset:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
5:freezer:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
4:devices:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
3:cpuacct,cpu:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
2:net_prio,net_cls:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f
1:name=systemd:/docker/74275930d9acfd7b4427769e77d695cce73b43c94bd37151f6b611ea509a817f