This repository has been archived by the owner on May 12, 2021. It is now read-only.
systemd cgroup paths not being handled correctly #2818
Labels
Comments
egernst
added
bug
fidencio
pushed a commit
to fidencio/kata-runtime
that referenced
this issue
Sep 7, 2020
Look at the provided cgroup path to determine whether systemd is being used to manage the cgroups. With this, systemd cgroups are being detected and created appropriately for the sandbox. Fixes: kata-containers#2818 Signed-off-by: Eric Ernsteernst <[email protected]> (cherry picked from commit ad5484b)
fidencio
pushed a commit
to fidencio/kata-runtime
that referenced
this issue
Sep 11, 2020
Look at the provided cgroup path to determine whether systemd is being used to manage the cgroups. With this, systemd cgroups are being detected and created appropriately for the sandbox. Fixes: kata-containers#2818 Signed-off-by: Eric Ernsteernst <[email protected]> (cherry picked from commit ad5484b)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description of problem
We currently fail to support systemd managed cgroups on the host (at least when sandbox cgroups only is utilized). We should auto-detect the cgroup manager being used on the system, and properly create sandbox cgroup accordingly.
We should be able to detect based on the format of the path being provided.
Expected result
A cgroup created under the system.slice for the appropriate subsystems, ie in docker case something like:
Actual result
Group created next to system.slice of format
system.slice:docker:SHAThe text was updated successfully, but these errors were encountered: