-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
WSL environment needs additional cgroupv2 configuration #3685
Comments
use the latest stable version from kind please and report back, also it seems you are using cgroupsv1 that has known issues |
May I know what is the stable version? |
the last one https://github.com/kubernetes-sigs/kind/releases , 0.23.0 in this case |
WSL2 + rootless podman is uncharted territory for us, but see these ~user contributed guides as well: |
I think cgroupv1 is going to be an issue, right?
|
Hi @stmcginnis Yes even i have tried with other image as well which is suggest by @aojea - image: kindest/node:v1.30.0@sha256:047357ac0cfea04663786a612ba1eaba9702bef25227a794b52890dd8bcd692e
|
OK, that does look like it may be part of the issue. I believe you will need to set up your WSL environment to be using cgroupv2. |
I'm really sorry i'm using windows machine how can i set wsl environment with cgroupv2.
|
And here the data inside podman machine ssh
|
Sorry, no idea as I haven't used WSL or Windows for a number of years now, but this looks like it may have some useful information: https://github.com/spurin/wsl-cgroupsv2 |
cgroup v1 can work but needs cgroupns suport. I would suggest using something like lima or docker desktop with docker instead, follow https://kind.sigs.k8s.io/docs/user/using-wsl2/ |
The failure to write cgroups isn't in kind, that's coming from podman after we ask it to create the container. |
I would guess cgroupns issues on this linux guest environment |
Hi @BenTheElder do I need to change any configuration from my side to make it work? |
I don't think this cgroup issue because when i have used below image i can see all the pods and up and running without any error message, do you have idea about this still i'm using cgroup v1 only according above podman info output.
|
Seems that I hit the same problem when trying to create a cluster on WSL 2 using the image Thank y'all for the hints. |
I recommend using a better supported platform than kind-on-podman-on-wsl2 Kubernetes uses docker on Linux primarily, some contributors use it on macOS. podman on WSL2 with cgroup v1 is probably the worst supported combination of options in the ecosystem and I can't personally replicate this, I'm not a windows user, and no windows users have helped us figure out a workable CI approach (e.g. previously we tried actions but could not run docker or podman in that environment). |
This is difficult to debug over github when we receive partial information, for example you say you're using this image but not with what kind version / environment, and with only excerpts from the logs. Have you looked at the suggestions above, including e.g. the complete guide for using WSL2? #3685 (comment)
Yes, I would highly recommend this. You can't create cgroup v2 clusters with Kubernetes < 1.19 but that's long out of support anyhow. Cgroup v2 is maturing and will be the focus for the ecosystem going forward, and in particular makes nested containers a lot more straightforward by typically having cgroupns enabled by default + the unified hierarchy. |
How did you fixed? Are you using mac book or windows system? |
I was able to create a cluster configuring WSL 2 to use |
We are good close this ticket issue has been resolved.
|
Thanks for all the contributions and guidelines |
Glad you got it working! /close |
@stmcginnis: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Awesome! We should probably add a note pointing to the WSL2 cgroupv2 guide in the WSL2 page? |
Thanks all |
Good point, we really should capture that. /reopen |
@stmcginnis: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What happened:
I'm have created kind cluster using kindest node with base image using config.yaml i can control plane and node are in read state but when i see application pod i can see some error related i don't see this error in older release version kindest/node:v1.27.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
logs
Environment:
kind version
): kind v0.18.0 go1.20.2 windows/amd64docker info
,podman info
ornerdctl info
):/etc/os-release
): windows 11kubectl version
):Client Version: v1.28.2 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.30.0
The text was updated successfully, but these errors were encountered: