![]() Whereas if you use a linux platform all the way through, the portability of your code increases. ![]() install libraries, configure databases, etc) will not be portable to your actual application servers. But if your target platform is linux, much of the code you've written to build out and maintain your environment (i.e. ![]() If your target platform is a mac, then great, write all of your code and build scripts on a mac. Well, the term "unix-like" should give the answer away: in my opinion, MacOS is NOT a substitute for developing, building, and testing on a real linux distribution. You might be asking yourself this question when macs themselves are unix-like environments. By booting into Windows directly from MacOS, the virtualization feature that you need for WSL2 will be enabled.Įnsure that the two checkboxes inside of the red square are unchecked.Īfter doing this, you should be good to go! Why Run WSL2 on Mac? Once you do that, you need to boot directly into windows by going to System Preferences > Startup Disk and boot into windows by selecting your Bootcamp partition. Ensure that you get a response from that command (You should see "VMX" in the response. To fix this, boot into MacOS, open a terminal, and run sysctl -a | grep. So you may run into this error, for example, if you've booted into windows from power-on. It turns out that this feature needs to be enabled by the BIOS, and can only be enabled on the MacOS side. You'll get this error when you mac hardware doesn't support CPU virtualization, which is odd because most macs since 2010 certainly do support it. WslRegisterDistribution failed with error: 0x80370102Įrror: 0x80370102 The virtual machine could not be started because a required feature is not installed.
0 Comments
Leave a Reply. |