✅ No Hyper-V or WSL needed so it doesn't intervene with Vagrant and VirtualBox.What I wanted to achieve with this setup: So I decided to try something else in order to keep my ability to run VMs with Vagrant without sacrificing much of the Linux experience I got on WSL. Running full desktop environments for tools that offer only a GUI is very unstable.Running background services inside WSL such as nginx or mysql is not yet supported.I depend a lot on Vagrant for web development and Hyper-V and VirtualBox don't play nice, leading to VMs not booting properly or randomly triggering a kernel panic.Docker volume mounts inside the WSL machine fails as Docker for Windows doesn't know the path to the WSL filesystem. ![]() WSL2 is great for giving you a taste of Linux on Windows, but the following problems made me go back to the drawing board: ![]() I decided to try out WSL to fill my needs, it worked fine for a bit, having integration with Docker in WSL2 was a big step up from WSL1 but the limitations started to show up sooner than I expected. Working with lots of servers I became quite attached to working with a shell, but I'm stuck using Windows because of the Adobe suite, the Stream Deck I use for macros, and other proprietary software that I don't have an alternative for. With updates, some of the things written below do not reflect the reality today, WSL2 is now pretty good, Windows Terminal even got a quake mode, and I moved my workflow to docker.
0 Comments
Leave a Reply. |