`cri-o configured with cgroupfs cgroup manager, but received systemd slice as parent`
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
Tried installing sysbox 0.6.5 on a fresh cluster, and after deploying the manifest, now pods no longer work in the cluster.
Describing the pods I can see this issue:
Warning FailedCreatePodSandBox 2s (x17 over 3m25s) kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = cri-o configured with cgroupfs cgroup manager, but received systemd slice as parent: /kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod368236bb_a128_48e2_a105_0b2c1c7a24e5.slice
It's a vanilla Kubernetes 1.28 cluster with Ubuntu 22.04 nodes, kernel 5.15.
Seems similar to https://github.com/nestybox/sysbox/issues/567, but it's kinda the opposite.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Sysbox 0.6.5 deployment manifest and the Kubernetes pod sandbox events showing the CRI-O cgroup manager error. Compare the behavior with issue 567 and inspect the cgroupfs/systemd settings on the Ubuntu 22.04 nodes. Done means pods can be created successfully on the described Kubernetes 1.28 cluster without this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, linux, ubuntu
- Domain
- devops, infrastructure, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100