In the Windows 10 Creators Update (build 1703, April 2017), this is natively supported. So you can now run Windows binaries from Linux… notepad.exe or any other .exe (the extension is needed and it needs being on your path, some older versions need the whole path) …and vice versa using one of the following: bash.exe … Read more
Note: See footnote at bottom of this answer for background on this Community Wiki. There are several possible paths to enabling Systemd on WSL2 (but not WSL1). These are summarized here, with more detail provided below. Option 1: Upgrade WSL to the latest application release (if supported by your system) and opt-in to the Systemd … Read more
If you run the command uname -a in WSL you should get a result that contains the version of your WSL. This should be something like Linux COMPUTER_NAME 4.4.0-18362-Microsoft …. the number 18362 in that output is your WSL version and it needs to be at least 19041 to be a WSL2 build (only WSL2 … Read more
Ok, so I got it working as follows. I have Ubuntu on windows, with anaconda python 3.6 installed. Download and install VcXsrv or Xming (X11 for Windows) from sourceforge(see edit below) sudo apt-get update sudo apt-get install python3.6-tk (you may have to install a different python*-tk depnding on the python version you’re using) pip install … Read more
Seems like a forwarding problem. WSL2’s interface is NAT’d, whereas WSL1 was bridged by default. WSL seems to do some “auto-forwarding” of ports, but only on localhost. However, sometimes this auto-forwarding mechanism seems to “break down”. The main culprit seems to be hibernation or Windows Fast Startup (which are both closely-related features). Does the problem … Read more
To be honest, when I first looked at this question, I thought it would be an easy answer. Oh how wrong I was. There are a lot of nuances to how this works. Let’s start with the fairly “easy” part, though. The main difference between the first method and the second: wsl by itself launches … Read more
Check your .dockerignore file. Possible it ignores needed files for copy command and you get failed to compute cache key error.
See this video, it helped me: https://www.youtube.com/watch?v=yCK3easuYm4 netsh interface portproxy add v4tov4 listenport=<port-to-listen> listenaddress=0.0.0.0 connectport=<port-to-forward> connectaddress=<forward-to-this-IP-address> for example netsh interface portproxy add v4tov4 listenport=3000 listenaddress=0.0.0.0 connectport=3000 connectaddress=172.30.16.3 Microsoft has published a little bit of information about this on their WSL1 to WSL2 comparison page
This answer seeks to help others avoid spending 1-2 hours troubleshooting and slowly finding disparate solutions for common problems when using WSL for the terminal in VS Code. It does not cover installing specific packages, but rather common ones that may not properly install as dependencies when installing things that do rely on their presence, … Read more
Root cause: inotify is not fully supported in the 9P filesystem protocol on WSL2. There are several github issues on the WSL project related to this, but perhaps the most relevant is #4739. Possible Workarounds: Try nodemon -L (a.k.a. –legacy-watch) as Simperfy suggested. Try running from the default ext4 filesystem (e.g. mkdir -p $HOME/Projects/testserver). Note … Read more