When I install sysbox on RKE2 I run into this issue: https://github.com/nestybox/sysbox/issues/567 I can fix it by using the patch for CRI-O that is show on the second to last comment but I'd like to switch kubelet back onto systemd instead. Does anyone know where the kubelet arguments are stored on the host machines (or elsewhere) so that I can manually repair the

--cgroup-driver

flag?

are you not using the containerd that comes with rke2?

In short, I'm not entirely sure what the cluster config is after the sysbox is installed. It makes a bunch of changes. The RKE2 cluster is a clean install that is using containerd. Once the sysbox install is run I do believe that CRI-O is used. I am super new to sysbox (like yesterday) so I may need to read more on it. Let me dig a bit deeper into the specifics of the container runtime after sysbox install so I don't waste anyone's time. Thank you!

what is it even doing? Just from glancing at that issue it looks like it’s reconfiguring rke2 to use cri-o instead of containerd?

Ya, so the gist of sysbox is that it uses a custom container runtime (I think - which is why I want to dig deeper) that enables the execution of systemd so that you can run things like Docker inside of containers. It's pretty cool but also super weird and new to me so I feel pretty green around the edges. It definitely makes some fundamental changes to rke2. The added issue here is that I'm also pretty new to rke2 so that doesn't help either.

you can run docker in containers on vanilla rke2 with dind, you shouldn’t need to go deploy a bunch of extra stuff to make that work…

Oh sweet! I ended up on sysbox because it's the default docker-in-docker solution for Coder-OSS which is the use case for this specific cluster. I'll take a look at plugging dind into Coder!