Well I survived the upgrade, but here are some quick notes about the holes I fell into.
First off, the upgrade was a bit finnicky:
LxssManageand restart THAT.
wsl -l -vto see what flipping versions of WSL things are even running. This is what helped me realise that in spite of several upgrade calisthenics, I had somehow managed to NOT upgrade anything.
wsl --set-version Ubuntu 2to convert the existing distro (Ubuntu in my case) to wsl version 2! The operative word here is convert: this can be slow and you are generally advised to just install a new distro instead of converting the existing distro’s file sytem or whatever.
wsl.exe --set-default-version 2
Also: upgrading breaks your hot module reloading so badly that you will cry and want your mommy. I’d clung on to WSL 1 for so long that I was only now running into this… and like a lot of folks, I hadn’t read this before setting out on my upgrade journey. So:
On the other hand, it makes docker niftier, related to which:
DOCKER_HOSTenv variable. In fact, go ahead and do
unset DOCKER_HOSTand then to be extra sure, also remove that from your
~/.bashrcand restart your shell.
docker infofrom inside your wsl terminal and your docker will oblige with a screenful of glorious info! You are connected! Woohoo!
In short, waaay more wahala than I had initially bargained for. I am not complaining though… especially about the HMR shenaniganry because I wouldn’t know an inotify API (seemingly the root cause) if it slapped me with a wet fish. I await whatever voodoo incantations inter-OS devs need to whisper at it.
(Googles, now curious…)
Oh look, it has a man page.