You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What you expected to happen:
kind starting a cluster without error.
How to reproduce it (as minimally and precisely as possible):
Get WSL2 (see below)
Use a Fedora 36 distribution (see below)
Start kind kind create cluster
Anything else we need to know?:
Was working flawlessly with the same Fedora version 2 weeks ago. I suspect that WSL2 got a kernel update since then that might have triggered this issue.
Environment:
wsl --version
Version WSL : 1.2.0.0
Version du noyau : 5.15.90.1
Version WSLg : 1.0.51
Version MSRDC : 1.2.3770
Version direct3D : 1.608.2-61064218
Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Version de Windows : 10.0.19045.2728
Re: #2731, we intermittently get issues with users on odd Kernels that are missing cgroups functionality or have broken cgroups, I wouldn't expect this on fedora however, though last I checked WSL did typically involve a windows specific init instead of systemd (which would be setting up the cgroups).
Fixed after update of WSL2 version (1.2.5.0). Kernel version unchanged after update.
wsl --version
Version WSL : 1.2.5.0
Version du noyau : 5.15.90.1
Version WSLg : 1.0.51
Version MSRDC : 1.2.3770
Version direct3D : 1.608.2-61064218
Version de DXCore : 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Version de Windows : 10.0.19045.2728
What happened:
Starting kind does not work anymore in my WSL2 environment.
kind create cluster --loglevel=debug --retain
leads to the following output:
It look familiar with #2731 but I'm not using a 5.17+ kernel.
Environment: WSL2, kind 0.18
3029766531.tar.gz
What you expected to happen:
kind starting a cluster without error.
How to reproduce it (as minimally and precisely as possible):
Get WSL2 (see below)
Use a Fedora 36 distribution (see below)
Start kind
kind create cluster
Anything else we need to know?:
Was working flawlessly with the same Fedora version 2 weeks ago. I suspect that WSL2 got a kernel update since then that might have triggered this issue.
Environment:
The text was updated successfully, but these errors were encountered: