ctalledo
commented
3 years ago Note: even after we add support for cgroups v2 to Sysbox (soon), using cgroups v2 requires a machine whose kernel was booted with cgroups v2. I know Fedora has made the transition to enabling cgroups v2 by default, but not sure if Ubuntu has done the same. If not enable by default, it can be easily enabled via GRUB and rebooting the host, but it's an extra step.
Due to the latest changes in Kind's docker-images entrypoints, Sysbox is not able to launch Kind's images, nor able to wrap Kind's images with our own Sysbox images as we have been doing since day one.
Kind's latest entrypoint modifications condition the support of user-namespaces to the activation of cgroup-v2 in the system. This approach conflicts with Sysbox as user-namespaces feature is always supported regardless of the cgroup configuration of the system. Aside from that, Sysbox doesn't support cgroup-v2 (yet), so currently we can't meet this requirement imposed by Kind.
For the time being we will continue to provide 'kindest/node' images as thin wrappers over Kind's ones. In the future, once all the above issues are solved, Sysbox users should be able to make direct use of Kind images -- although technically speaking that will always depend on the restrictions/assumptions imposed by Kind's images entrypoint.
In the meantime, till we generate the new
kindest/nodeimages for v1.20 and v1.21 (which are the ones impacted by this issue), we suggest to continue utilizing the existingnestybox/kindest/node:v1.18andnestybox/kindest/node:v1.19images.