I have successfully installed WSL 2 and Ubuntu on my windows machine. If I start PowerShell and type bash it successfully starts bash.
However if I run PowerShell as Administrator and type bash I get the following message:
Windows Subsystem for Linux has no installed distributions.
Distributions can be installed by visiting the Microsoft Store:
https://aka.ms/wslstore
Worst part is that I'm pretty sure this worked yesterday(!)
Related
Currently I'm working on testing a github repository and I'm following the github's README.md that requires me to run "bash build/build.sh" command line to build environment. But I somehow could not make the command run in my PowerShell. Windows PowerShell keeps showing "Windows Subsystem for Linux has no installed distributions.
Use 'wsl.exe --list --online' to list available distributions
and 'wsl.exe --install ' to install.
Distributions can also be installed by visiting the Microsoft Store:
https://aka.ms/wslstore
Error code: Bash/Service/CreateInstance/GetDefaultDistro/WSL_E_DEFAULT_DISTRO_NOT_FOUND"
I have installed the Windows Subsystem for Linux Preview from Microsoft Store but I still could not run the "bash build/build.sh" command.
Question solved. I have solve it by following this youtube video.
https://youtu.be/mDmpnkjETpw
Basically you have to check two boxes in the "Turn Windows features on or off" before start trying out the Linux command.
Virtual Machine Platform
Windows Subsystem for Linux
Thanks for viewing.
I'm trying to set up a web development environment using a guide on Medium. The author says we need to install Git for both Windows and for Windows Subsystem for Linux. Git takes up a lot of space. Do we need to install it twice?
I have Visual Studio Code and Ubuntu (WSL). I also installed Git for Windows 10.
Git For Windows differs from the Linux Git.
So, if you want to execute commands in a Windows CMD and a Linux WSL shell, then yes, you would need to install both.
On Windows side, that can mean simply uncompressing the self-extracting archive PortableGit-2.22.0-64-bit.7z.exe anywhere you want, and add it to your PATH.
I am looking for a possibility to copy a file from Windows to a Linux machine, and my Windows machine will not have Cygwin installed .
The command I am trying is
linux #> scp windows-machine:e:\file.txt
Since you say "my windows machine will not have cygwin installed", I'm assuming you cannot install arbitrary software on the Windows side but that you have control of the Linux machine. Under those assumptions, you can use the Windows FTP client to transfer files to the Linux machine. (Of course, you will have to enable the FTP daemon on the Linux machine, most likely via inetd or systemctl.)
In my system I have enabled the Windows Subsystem for Linux(WSL) and installed Ubuntu on Windows 10.
https://github.com/fabric8io/fabric8-platform/blob/master/INSTALL.md
On top of the WSL, I was trying to install the fabric8 from the scratch with the Minishift using instructions for Ubuntu in the above link and while running the below command, getting error stating that "No User home environment variable found for os windows"
gofabric8 start --minishift --package=system --namespace fabric8
Note: Before running the above commands, I have setup libvirt and qemu-kvm in my WSL
I had the same problem installing fabric8 on Windows. A look into the sourcecode reveals, you need to define a HOME environment variable. In windows CMD try
set HOME=C:\Users\yourHome
That worked for me
I have Docker installed on Windows 7 platform. However when I try to run boot2docker start, the console gives me:
Failed to get machine 'boot2docker-vm': machine does not exist.
Ok, so I try to initialize the machine: boot2docker init. What now happens is even though I have the ISO image on the same path as docker, it tries to download a new image (and then fails to do so).
I uninstalled both OracleVM and GIT before installing them with boot2docker bundle as advised on Docker forums, but now I don't know how to proceed.
I had the same problem on a Windows 7 64 bit system when I installed the entire boot2docker package. It seems that running the solely 64-bit based boot2docker image from a 32-bit OS image (e.g. created by Virtualbox) does not work.
The solution for me was
to activate Intel Virtualisation Technolologies in my BIOS
(Lenovo X61 for me). Note that the settings can be found either
under CPU or Security.
choose a 64 bit OS version in VirtualBox and boot in with the
image obtained by boot2docker.
In case you're trying to do this now
For Windows 10 64-bit: Pro, Enterprise, or Education (Build 15063 or later), follow the instructions to install Docker Desktop here https://docs.docker.com/docker-for-windows/install/.
If you have Windows systems that do not meet the requirements of Docker Desktop for Windows(in my case Microsoft Windows 10 Home Single Language), you can install Docker Toolbox by following the instructions here https://docs.docker.com/toolbox/toolbox_install_windows/.
boot2docker does not support sharing directories on Windows IIRC. The way I run Docker on windows is:
install VirtualBox
install Vagrant
create a directory (let's say c:\vm\docker)
download this Vagrantfile and save it under c:\vm\docker\Vagrantfile
open a DOS command prompt
go to the directory cd c:\vm\docker
start the VM vagrant up and wait for it to install, start up and get provisionned
connect to the VM vagrant ssh
play with docker docker images, etc
Also you might want a real console instead of using the DOS command prompt:
install Git Bash for Windows
install Console
setup Console to use Git Bash (see this guide)
use Console to run the vagrant up and vagrant ssh commands