-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kind
cluster creation fails
#5092
Comments
I can reproduce this on both an intel-mac and ubuntu, so I'm assuming something is needed in the Lima VM. Reformatting the above session so it's easier to read:
Without quotes it's hard to parse that final |
Some other output while in
|
From kubernetes-sigs/kind#3277 (comment) it looks like this is a limitation caused by our VM being based on |
We have an open issue to investigate switching to cgroupv2: #4141. |
On cgroupv2 cgroupns=private is the default, but it's settable on v1. docker/podman both change the default based on v1/v2 unless the user overrides it, but there's no reason it can't be enabled on v1. The problem seems to be on these alpine hosts (with the unusual init?) cgroupns=private containers fail (the change in kind v0.20.0), this client flag was added in docker 20.10.0 released 2020-12-08. |
I can confirm the same error with KinD running against Colima on an arm based mac... |
I've tentatively added this to the 1.11 milestone to investigate if we can make it work with Alpine/OpenRC. |
The same issue is also effecting buildx build issues, when you create a new buildx instance. Using the default instance is fine, so its the new container created as part of the |
Any news on this? Seems like it was removed from the 1.12 milestone and no fix in sight. Currently, neither rancher desktop nor colima support kind. I really like Rancher Desktop and want to recommend it in our org, without kind support it's hard to do so. |
I'm sorry, but I'm not aware of any way to get The best I can suggest at this time is to try out k3d, which is similar to |
If someone has time to debug this further kind maintainers can review incoming patches or debugging information if it turns out to be a bug in kind but I'm not realistically able to focus on this specific host anytime soon. For the moment you'll need a different pairing of tools, there are some suggestions in the linked kind issue above. |
Actual Behavior
Attempting to create a K8s cluster using
kind
fails on thepreparing nodes
step.Steps to Reproduce
$ kind create cluster
Result
Expected Behavior
The cluster is created without error
Additional Information
Works fine on both Docker Desktop and Podman Desktop.
Rancher Desktop Version
1.9.1
Rancher Desktop K8s Version
N/A
Which container engine are you using?
moby (docker cli)
What operating system are you using?
macOS
Operating System / Build Version
macOS Ventura 13.4.1
What CPU architecture are you using?
arm64 (Apple Silicon)
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
No response
The text was updated successfully, but these errors were encountered: