Rodny Molina

@dgadelha, thanks for the repro steps. Will take a look at this one within the next few days.

@gdraganic, I think that's pretty much the issue here... The sysbox daemon-set should not have switched the RKE2's kubelet to `cgroupfs` if RKE2 has originally picked `systemd` as its cgroup...

@FFock, thanks for filing this issue. I would need to reproduce this one locally to identify the fix, but at first glance, I see room for the behavior that you're...

By looking at your initial logs, it looks like kubelet is struggling to find the `pause` image, which in cri-o's setups is typically configured within its default config file: `/etc/crio/crio.conf`....

> Pulling the k8s.gcr.io/pause:3.5 image on the node using docker pull does not fix the issue too. Is this initializing code downloading the image in a docker-in-docker environment? During installation,...

Haven't looked in details but i believe the proper config file is [containers.conf](https://github.com/containers/common/blob/main/docs/containers.conf.5.md). You will need to add something like this within the "engine" section and then restart crio: ```...

Excellent @FFock. Let's leave this issue open till we implement a proper solution in our sysbox-k8s-deploy daemonset.

@fhaefemeier, not sure I got that. Leaving aside the fact that the original issue deals with a k8s setup and you are referring to a standalone / non-k8s deployment, why...

@FFock, I don't see how adding two global vars in your `crio.service` file can cause something like this. Looks like the crio daemon is not able to initialize for some...

We should have this (the proxy thing) fixed shortly anyways. Will ping you when done.