podman

mirror of https://github.com/containers/podman.git synced 2025-06-05 05:57:24 +08:00

Files

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_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

cgroups.go

cgroup: skip unified if we are using v1