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