Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
create/run/exec: refuse a frozen cgroup
This bugged me a few times during runc development. A new container is run, and runc init is stuck, 🎶 and nothing ever happens, and I wonder... 🎶 Figuring out that the cause of it is (pre-created) frozen cgroup is not very obvious. In fact, we should not try to run a new runc init process if a cgroup is frozen -- nothing good will come out of it. Add a check that the container cgroup is not frozen before trying to start runc init. A (very bad) alternative to that would be to thaw the cgroup. Add a test case checking that all three runc commands (create, run, and exec) refuse to proceed if the cgroup is frozen. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
- Loading branch information