mirror of
https://github.com/containers/podman
synced 2024-10-20 09:13:46 +00:00
4d800a5f45
When we create a container, we assign a cgroup parent based on the current cgroup manager in use. This parent is only usable with the cgroup manager the container is created with, so if the default cgroup manager is later changed or overridden, the container will not be able to start. To solve this, store the cgroup manager that created the container in container configuration, so we can guarantee a container with a systemd cgroup parent will always be started with systemd cgroups. Unfortunately, this is very difficult to test in CI, due to the fact that we hard-code cgroup manager on all invocations of Podman in CI. Fixes #7830 Signed-off-by: Matthew Heon <matthew.heon@pm.me> |
||
|---|---|---|
| .. | ||
| annotations.go | ||
| config.go | ||
| container_inspect.go | ||
| containerstate.go | ||
| errors.go | ||
| exec_codes.go | ||
| healthchecks.go | ||
| info.go | ||
| pod_inspect.go | ||
| podstate.go | ||
| runtime.go | ||
| version.go | ||