k3s single node in wsl2 takes ~4min to be ready

[ghost]

Hi,

I'm currently working in a project that involves k3s single node cluster running on wsl2 with ubuntu 18.04, when I turn off the Windows OS or execute a wsl --terminate , the node takes about 4min to be ready, looking into the k3s log I can see a loop while the node is ready like this:
Failed to create existing container: /kubepods/besteffort/podebb6e02a-3dba-46ff-83eb-f2658f3c112e/c0252344011d2725c9d8ed099aad16f9c3cf775385793211b34fe90b2745be64: task c0252344011d2725c9d8ed099aad16f9c3cf775385793211b34fe90b2745be64 not found: not found
Skipping pod synchronization" err="container runtime status check may not have completed yet"
setters.go:577] "Node became not ready" node="raider" condition={Type:Ready Status:False LastHeartbeatTime:2021-07-06 21:13:27.4980269 +0000 UTC m=+31.496884001 LastTransitionTime:2021-07-06 21:13:27.4980269 +0000 UTC m=+31.496884001 Reason:KubeletNotReady Message:container runtime status check may not have completed yet}

Tried configuring GracefulNodeShutdown feature, setting the options:

"--kubelet-arg 'node-status-update-frequency=4s'"
"--kube-controller-manager-arg 'node-monitor-period=2s'"
"--kube-controller-manager-arg 'node-monitor-grace-period=16s'"
"--kube-apiserver-arg 'default-not-ready-toleration-seconds=20'"
"--kube-apiserver-arg 'default-unreachable-toleration-seconds=20'"

But none of these seem to work.

Please could you help with some ideas?

Thanks in advance.