kind 0.13.0 does not work with Colima v0.4.1 #291
Comments
longwuyuan
changed the title
longwuyuan
changed the title
|
This is probably not a colima bug, it is that systemd is not in use I think (based on #212 (comment)) and kind v0.13.0 is currently broken on non-systemd hosts when running kubernetes v1.24+ (the default is 1.24.0) I would encourage the project to consider shipping systemd, as this is trending as "default" supported cgroup driver option for cgroupsv2 in kubernetes, containerd and so on as far as I can tell, but that's a different discussion and kind not working here is something we should resolve on the kind side (assuming that this is in fact due to lack of systemd + kubernetes-sigs/kind#2765) |
|
@longwuyuan was it working fine on version v0.3.4? |
|
Alpine uses rc-init (AFAIK and I checked on my Colima qemu vm too) so until confirmed, its almost certain that is the root cause. Thanks tons @BenTheElder . So for now, manually downloading kind v0.12.0 and ensuring its in the path is the workaround. But I guess the cgroupsv2 factor has big implications here. Will wait for any updates. |
|
hi @abiosoft , I was using I don't know how to check if I had Colima v0.3.4 last week. I will google for brew syntax for that (if feasible now and update). But from what @BenTheElder mentioned, systemd init being a requirement and alpine not using systemd, seems like a big deal here, as per my limited knowledge. |
|
We didn't intend to require systemd on the host and consider that a bug in kind. Where at all possible kind should ideally just work where containers work (excluding for example, missing kernel modules required by kubernetes). But I would recommend considering systemd for running containerd in the future, independent of any kind issues. |
|
@BenTheElder kind project considering systemd requirement a bug is good to know. Thank you very much. Did you mean the workaround being |
|
@abiosoft , I have workaround now. But latest kind is apparently broken with latest Colima. Do I close the issue or you prefer this issue be kept open for tracking. |
Thanks for the suggestion @BenTheElder. Ubuntu is a bit too bloated and the minimal image is limited to x86. Any other recommendations in this regard?
@longwuyuan the issue can be left open for tracking. Thanks. |
|
We have a working fix pending now kubernetes-sigs/kind#2778 (comment)
I'm not sure for lima / vm images, this is the first I've used lima. Perhaps something like flatcar? Re recommendation BTW: https://github.com/opencontainers/runc/blob/main/docs/cgroup-v2.md#systemd
https://kubernetes.io/docs/setup/production-environment/container-runtimes/#cgroup-drivers (containerd guide has you setup systemd, cri-o already uses it by default, docker is no longer a runtime) |
Yeah, they are lightweight, however the cloud images are not :( @longwuyuan Lima technically does not provide Docker (or anything) per se, it mainly provides an easy way to run VMs with cloud images. However, it does come with sample configurations of which one of them is for Docker. Colima utilises Lima to run the VM, and also perform other configs to make it an easier experience for the end user. Usually those that could care less about the details and simply wants Docker/Containerd/Kubernetes.
The decision to go with Alpine is due to the light image size, the ease of bundling dependencies and the support from Rancher Desktop. (Colima uses a fork of Rancher Desktop's image). If there is a possibly of generating a similar Ubuntu/Debian image, that can work. PS: Colima actually used Ubuntu initially but switched to Alpine from v0.3.0. |
|
@abiosoft understood. Thank you very much for Colima. Simply awesome solution 🙏 |
|
I have tested kind v0.14.0 and it works with Colima. Thanks @BenTheElder. |
Hi,
kind create cluster --name devworks with kind version 0.12.0 but is broken with kind version 0.13.0.kind version 0.13.0 installed by brew.
On macOS Monterey on intel-Mac Pro, I am getting the error copy/pasted below, when I tried creating kind cluster ;
The text was updated successfully, but these errors were encountered: