rancher-desktop icon indicating copy to clipboard operation
rancher-desktop copied to clipboard

Please lower the needed WSL Kernel Version back to 5.4 because of second most commented WSL Bug

Open benzman81 opened this issue 1 year ago • 2 comments

Actual Behavior

RD 1.13 now needs WSL Kernel Version >=5.15.

Steps to Reproduce

None

Result

Because of the second most commented Bug for WSL https://github.com/microsoft/WSL/issues/6982#issuecomment-1949892016 we are now no langer able to update RD as of its kernel restriction. The last known Kernel version for WSL not having problems with hibernate is 5.4.

Expected Behavior

Maybe consider reverting the restriction to 5.15 for RD to just not support the features that required this restriction rather than not supporting lower versions at all.

Additional Information

No response

Rancher Desktop Version

1.13

Rancher Desktop K8s Version

0.0.0

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 10

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

benzman81 avatar Mar 13 '24 20:03 benzman81

The kernel issues are because we bumped to alpine 3.19, which upgraded iptables to use the nftables backend (as I understand it), and older kernels no longer worked with it. See #6443 for the initial issue.

If we can figure out a way to get iptables to work (e.g. figure out how to use iptables-legacy instead, or something similar), we can then drop the kernel version requirement. However, that will probably be relatively low priority, so help tracking the steps down (even if not in the form of a PR) would be much appreciated and would help moving this forward.

Unfortunately, not supporting the relevant features means dockerd / containerd wouldn't work, so that would render Rancher Desktop kind of moot.

mook-as avatar Mar 13 '24 21:03 mook-as

ah, thats a bummer. I don't think I can help with that. So I am stuck with 1.12.x, I guess.

benzman81 avatar Mar 15 '24 10:03 benzman81

This has been addressed in the 1.13.1 release, which switches back to iptables-legacy when the kernel is too old.

jandubois avatar Apr 05 '24 19:04 jandubois