The Ultimate #WSL2 Guide - Part 1 - Tour

In this video you will learn from my pain of migrating from VirtualBox to WSL2. This video is just a tour. The next one is a step by step guide to replicate my setup.

WSL docs:

Expanding the size of your WSL2 virtual hard drive:

Step by step guide to replicate my setup:

This video is part of the following playlists:

Table of Contents
00:00 intro
01:26 the goal
04:08 the outside tour
06:30 what is WSL all about?
11:49 the inside tour
34:45 conclusion

Cheers and Happy Coding!

#WSL #VirtualBox

[DevInsideYou]

Table of Contents
00:00 intro
01:26 the goal
04:08 the outside tour
06:30 what is WSL all about?
11:49 the inside tour
34:45 conclusion

[Winnetou]

At 25:50, regarding the default WSL: in the verbose output, the default is marked with a star :)

[ZsoltDonca]

Just out of curiosity, what is keeping you back from using Linux full time? I'm guessing it's some unsupported software, or maybe hardware.

[Tobwilk]

What headset are you using? It sounds great.

[oplavevski]

How were you able to run Sublime from the WSL on to Windows? Can you describe your approach?

[tridibbiswas]

Hi, Thank you for the video. I am a newbie to this. Have installed using Ubuntu on WSL2 on Windows Terminal with zsh. But I find that there is gap/space on the right hand side, bottom of the screen and the zsh screen does not cover the entire terminal window edge to edge. How could we fix this. Is there something I am missing
. I have noticed the same when I use the bash shell as well.

[TuxxFF]

Still a Homestead/vagrant is a better solution than wsl2, so many little issues happening with wsl2 at least when it comes to development.
With homestead i can setup a php version project, i have a full linux box same as the one you would get from Linode or digital ocean.
In my case the thing that is keeping me from going back to windows is the poor development experience it offers.

[eduardmart]

Cool! Really thorough explanation! The bent on YouTube!

Btw do you happen to know a way to stop all WSL processes with simple command, and don't run it until explicitly said to do so?
What about docker for windows? I know that it's a power hog. I consumes all the recourses, on my old hardware I couldn't even properly move mouse cursor after I had started a docker container.
Is there a simple way to stop all the docker-related processes? (without reboot)

For instance - I started docker container, used some commands in WSL2 and then want to play some computer games - let's it be The Witcher 3. How do I stop all that junk that wsl2 + docker creates to make the game playable? Is it even possible?