Skip to content

systemd-cgroup support #193

@joost14

Description

@joost14

Hello,

I'm trying to setup Kubernetes(kubeadm) + CRI-O + runsc. I'm enabling the runtimes through the alpha feature gate RuntimeClass (crio is dropping support for untrusted-workload). I've got it to work with some other runtimes already, but I'm having some issues when trying to run runsc.

The error when I'm starting the pod is the following:
kubelet, k8sworker01 Failed create pod sandbox: rpc error: code = Unknown desc = container create failed: flag provided but not defined: -systemd-cgroup

Crio config file:

  [crio.runtime.runtimes.runsc]
  runtime_path = "/usr/local/bin/runsc"

I was wondering if anyone got runsc working with kubernetes and crio yet.

Edit: when switching the cgroup-manager within the crio config from systemd to groupfs the container wont start at all. Error:
kubelet, k8sworker01 Failed 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-pode9fd6274_59d1_11e9_af90_9e3c8464d679.slice

Edit2:
Solved it by changing systemd to cgroupfs in crio.conf and in '/etc/default/kubelet':
' KUBELET_EXTRA_ARGS=--cgroup-driver=cgroupfs'

That leaves me with the following question; is 'systemd' not supported yet for gvisor?

Metadata

Metadata

Assignees

Labels

area: compatibilityIssue related to (Linux) kernel compatibilityarea: integrationIssue related to third party integrationspriority: p2Normal priorityruntime: cri-oIssues related to cri-otype: bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions