Peter Hunt f4b59c74a7 cgroup: skip unified if we are using v1 ... There exists a chance for a node to be booted in v1, but have reminents of v2. An example is this CRI-O ci run: https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gcs/origin-federated-results/pr-logs/pull/cri-o_cri-o/3565/test_pull_request_crio_critest_fedora/11243/ We fail because we are incorrectly writing to the unified path, because we are v1. We should not write to the unified path if we are v1 Signed-off-by: Peter Hunt <pehunt@redhat.com>		2020-05-12 15:36:33 -04:00
..
blkio.go	cgroups: attempt a recursive rmdir	2019-07-11 18:07:48 +02:00
cgroups.go	cgroup: skip unified if we are using v1	2020-05-12 15:36:33 -04:00
cgroups_supported.go	Use cgroupv2 super magic from golang.org/x/sys/unix	2020-01-21 16:08:29 +01:00
cgroups_unsupported.go	rootless: automatically create a systemd scope	2019-09-12 08:35:26 +02:00
cpu.go	stats: add SystemUsage	2020-02-12 11:58:29 +01:00
cpuset.go	cgroups: attempt a recursive rmdir	2019-07-11 18:07:48 +02:00
memory.go	cgroups: attempt a recursive rmdir	2019-07-11 18:07:48 +02:00
pids.go	Fix invalid container path comparison for pid cgroup	2020-04-14 11:02:42 +02:00
systemd.go	update systemd & dbus dependencies	2020-03-10 18:34:55 +01:00