windows-subsystem-for-linux

问题 I am using Windows 10 and have Python installed. The new update brought bash to windows, but when I call python from inside bash, it refers to the Python installation which came with the bash, not to my Python installed on Windows. So, for example, I can't use the modules which I have already installed on Windows and would have to install them separately on the bash installation. How can I (and can I?) make bash point to my original Windows Python installation? I see that in /usr/bin I have a

问题 I am using Windows 10 and have Python installed. The new update brought bash to windows, but when I call python from inside bash, it refers to the Python installation which came with the bash, not to my Python installed on Windows. So, for example, I can't use the modules which I have already installed on Windows and would have to install them separately on the bash installation. How can I (and can I?) make bash point to my original Windows Python installation? I see that in /usr/bin I have a

问题 When trying to use the Linux version of Oracle's JDK on the latest Windows 10 build having support for bash, I am running into a problem with the prompt hanging whenever attempting to invoke the java binary. Typing even something as simple as java -version hangs and I have to terminate the process to resume control. Anyone got this working yet? 回答1: I wanted to clarify that as of 9 December 2016, you most certainly can install Java 8 on Ubuntu Bash for Windows 10 and that @Karl Horton is

问题 According to the documentation of Vagrant, the topic WSL and Vagrant is advanced. You need to install Vagrant on Linux, because: While the vagrant.exe executable provided by the Vagrant Windows installation is accessible from within the WSL, it will not function as expected. But I don't want to run Vagrant primarily in Linux. I would like to use Virtual Box, installed on my Windows 10 host. But I don't want to leave Linux bash, just to start Vagrant. Is there a way to remote control Vagrant

问题 I have just installed WSL with Ubuntu 18.04. I am running Windows 10 Pro on inside track with version 18922.rs_prerelease.190614-1427 I used this guide: https://docs.microsoft.com/en-us/windows/wsl/install-win10 Then I converted the WLS to WSL2 using this guide: https://docs.microsoft.com/en-us/windows/wsl/wsl2-index PS correctly shows my distro running in WSL2: PS C:\WINDOWS\system32> wsl --list --verbose NAME STATE VERSION * Ubuntu-18.04 Running 2 I am using git on the distro and have

问题 I have just installed WSL with Ubuntu 18.04. I am running Windows 10 Pro on inside track with version 18922.rs_prerelease.190614-1427 I used this guide: https://docs.microsoft.com/en-us/windows/wsl/install-win10 Then I converted the WLS to WSL2 using this guide: https://docs.microsoft.com/en-us/windows/wsl/wsl2-index PS correctly shows my distro running in WSL2: PS C:\WINDOWS\system32> wsl --list --verbose NAME STATE VERSION * Ubuntu-18.04 Running 2 I am using git on the distro and have

问题 when i Turn on Windows Subsystem for Linux option in Windows features on or off VirtualBox out an error every time i run a vm Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} is there a way to fix the VirtualBox error without turn off wsl 回答1: I found it! After much research, and trial and error, here is what enabled me to run VMs

问题 Today I got this error message: "WSL not found at: C:\Users\Nick\AppData\Local\Microsoft\WindowsApps\debian.exe" Before this message today, everything worked fine (I start Debian through start menu, restart the ssh service, then start CLion and it linked up just fine.). The executable is there, just 0kb. The strange thing is that the Linux environment can be opened from windows as always (debian), I can ssh into it just fine (looks like CLion can as well, see picture). This happened after an

问题 I'm using Window Linux Subsystem (Debian stretch). Followed the instruction on Docker website, I installed docker-ce, but it cannot start. Here is the info: $ sudo service docker start grep: /etc/fstab: No such file or directory [ ok ] Starting Docker: docker. $ sudo service docker status [FAIL] Docker is not running ... failed! What should I do with /etc/fstab not found? 回答1: I was getting the same error. Apparently on my install of WSL with Debian, I didn't have an etc/fstab file.

问题 I'm a very first user of Ubuntu. I failed to install Ubuntu in wmware ,so I installed Ubuntu application in Microsoft app store and everything was quite all right. But when I insert shutdown or halt command to power off my ubuntu I kept getting 'system has not been booted with system as init system (PID 1). Can't operate' error message. I tried to using docker following with this link (https://blog.jayway.com/2017/04/19/running-docker-on-bash-on-windows/) but I failed after going to Number 2