Microsoft are already previewing, and getting close to releasing a wayland graphics subsystem for WSL2.

It will be a big step forward from the various X server options & is looking very promising.

Personally I am really liking WSL2- it has replaced an always on Linux VM for me (well, it is an always on Linux VM for me).

> it has replaced an always on Linux VM for me (well, it is an always on Linux VM for me).

Here's a question I've been dying to ask someone who admits this is just a VM: What makes it better than running VirtualBox or VMWare Workstation, and having a nice GUI to control the various elements of the virtualization settings?

The major benefits over a fully managed VM from my exp. with it have been

- easy integration with the Windows filesystem (it's automounted into the WSL env)

- Using VS Code to work with files in the WSL2 env. works out of the box (just type `code .` in a WSL windows)

- It's very quick to spin up new WSL2 instances. you can just use `--import` and it'll bring in a tarball to create your new instance. You can even export a Docker image and use that as a WSL instance base filesystem which is handy.

- Docker for Windows works pretty well for most usecases and you get one shared Docker instance across all your WSL setups.

Sure I could do all that with discrete managed VMs but this is easier

Do you know if docker and minikube work inside wsl2? I loaned my only windows machine to a colleague and won't get it back for a week or two, otherwise I would check it out myself.

TBH for throwaway Kubernetes cluster in WSL, I'd recommend kind (https://github.com/kubernetes-sigs/kind) it works just fine with WSL/Docker for Windows.