f158ac45ef
Setting `cgroup-driver=systemd` was originally necessary to match with docker, else the kubelet would not start (#111835) However, since then, docker support has been dropped from k3s (#177790). As such, this option is much less necessary. More importantly, it now seems to be actively causing issues. Due to an upstream k3s bug, it's resulting in the kubelet and containerd having different cgroup drivers, which seems to result in some difficult to debug failure modes. See https://github.com/NixOS/nixpkgs/issues/181790#issuecomment-1188840862 for a description of this problem. Removing this flag entirely seems reasonable to me, and it results in k3s working again on my machine. |
||
|---|---|---|
| .. | ||
| corosync | ||
| hadoop | ||
| k3s | ||
| kubernetes | ||
| pacemaker | ||
| spark | ||