[LINUX] Points to note when updating to WSL2

Purpose of this time

Update WSL1 that was originally used to WSL2

Update flow

MS has published the official document, there are many articles if you ask google teacher, so basically there is no problem if you follow it. There was one thing that didn't suit my environment.


If the result of> wsl --set-default-version is an invalid command, enter wsl --help. If you don't see --set-default-version, it means it's not supported by your OS and you need to update to version 1903, build 18362 or higher.

It simply says version 1903, build 18362, but this version did not improve the above symptom, and when I updated to version 1909, build 18363.1049, --set-default-version was displayed. I do not know the cause and I can not say anything because it is a verification of only one unit, but if you have the same symptom, you may try updating the build version to the latest.

Recommended Posts

Points to note when updating to WSL2
Points to note when switching from NAOqi OS 2.4.3 to 2.5.5
Points to note when performing logistic regression with Statsmodels
Points to note when deleting multiple elements from the List
(Note) Points to be addicted to when installing Scilab on ArchLinux
Points to note when making pandas read csv of excel output
Python Note: When assigning a value to a string
What I did when updating from Python 2.6 to 2.7
Transition from WSL1 to WSL2
Things to note when initializing a list in Python
Note to daemonize python
What to do when a Remove Error occurs when updating conda
[python] A note when trying to use numpy with Cython
Precautions when upgrading TensorFlow (to 1.3)
[Note] How to use virtualenv
A note I was addicted to when making a beep on Linux
Things to note when running Python on EC2 from AWS Lambda
Atom: Note for Indentation Error when copying Python script to shell
[Note] Items to check when an infinite loop occurs in pyenv
A note I was addicted to when creating a table with SQLAlchemy
When WSL Distro fails to start (error: "WslRegisterDistribution failed with error: 0x800706be.")