Files
podman/pkg
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
..
2020-05-12 08:35:48 -05:00
2020-05-12 10:20:48 +02:00
2020-05-12 08:35:48 -05:00
2019-07-23 15:43:40 -04:00
2020-03-05 20:03:44 +01:00
2018-03-27 21:55:33 +00:00
2020-03-05 20:03:44 +01:00
2019-12-12 19:53:46 -03:00
2020-03-09 09:03:51 +01:00
2020-05-11 13:02:33 +02:00
2020-01-13 14:27:02 +01:00
2020-01-14 09:54:48 +01:00
2020-05-07 09:55:52 -05:00
2020-05-01 15:00:33 -04:00
2020-03-30 08:18:35 -07:00
2020-05-05 08:46:51 -05:00