Windows 10: Difference between docker ps and wsl -l -v

gabrielwu84 · Oct 6, 2020

Hi,

Can I check what entities are being displayed when I run wsl -l -v and how it relates to the docker containers displayed when docker ps is executed?

I am trying to run multiple instances of the same WSL ubuntu version, and I boiled the issue down to this question. Any advise on the matter is greatly appreciated!

Best regards,

Gabriel

:)

NickJP · Oct 7, 2020

Cannot upgrade installed distros in WSL to version 2

After installing the Win10 2004 build 19041 update (running winver shows "version 2004 (OS build 19041.388)", I've tried to upgrade a couple of installed distros I had in WSL version 1 to WSL version 2 following the instructions at https://docs.microsoft.com/en-us/win.../install-win10. All the steps in the instructions compete successfully, up to the point where I try to change the WSL version of one of the installed distros to 2 at which point I see the messages below:

Code:

PS C:\WINDOWS\system32> wsl -l -v
NAME STATE VERSION
* Debian Stopped 1
Ubuntu-20.04 Stopped 1
PS C:\WINDOWS\system32> wsl --set-version Debian 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit About Windows Subsystem for Linux
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/wsl2-install
PS C:\WINDOWS\system32> wsl -l -v
NAME STATE VERSION
* Debian Stopped 1
Ubuntu-20.04 Stopped 1
PS C:\WINDOWS\system32>
Click to expand...

I have enabled the Virtual Machine Platform feature (it shows as on with a tick against it in Control Panel Windows features), Intel-vt virtualization is enabled in the BIOS, and running msinfo32 shows, at the bottom of the system summary listing:

Code:

Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes
Click to expand...

I also tried installing another distro with the WSL default version set to 2, but attempting to launch it shows the error:

Code:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Error: 0x80370102 The virtual machine could not be started because a required feature is not installed.

Press any key to continue...
Click to expand...

Any suggestions on how to get around this problem? From what I've read, WSL2 gives worthwhile speed increases over WSL1, and so is worth using if I can get it to work.

Tri Nguyen · Oct 7, 2020

Docker client on WSL cannot connect to Docker for Windows

I have docker set up on my Windows machine with WSL like this:
(similar to what's described here Running Docker on Windows Subsystem for Linux (WSL) : docker)

Installed Docker for Windows

Installed the docker client inside WSL

export DOCKER_HOST=tcp://127.0.0.1:2375

However, when I run docker ps, I get this error:

Cannot connect to the Docker daemon at tcp://127.0.0.1:2375. Is the docker daemon running?

I know that docker is running, and if can get docker.exe ps ok from the Windows CMD.

I had this working before, but it doesn't seem to work now. I have updated the Docker for Windows app to the latest version, and restarted my machine a couple times.

Does anyone knows if there's something I could try?

Cluster Head · Oct 7, 2020

Create and run Hyper-V containers using Docker on Windows 10 desktop

Create and run Hyper-V containers using Docker on Windows 10 desktop

As you probably know the Windows Insider program allows to get preview Windows 10 builds to test the new features that are coming in the next major update of Windows. Since a few weeks, a new feature named Container has been included in Windows 10 preview builds. This feature brings Hyper-V containers on the desktop, natively.

There are two different kind of containers on Windows : Windows Container and Hyper-V Container. They work in the same way, instead of that Hyper-V containers are more isolated than Windows Container because they are running in a very lightweight virtual machine that provides kernel isolation and not just process isolation.

For more information about Hyper-V containers, check the official documentation on MSDN: Hyper-V Containers

You want to try it? It’s pretty simple! First, you need to enroll your machine in the Windows Insider program (see link above) and get the latest build from the insider fast ring.

Once done, just open the Turn Windows features on or off, then select Containers and Hyper-V in the list:

Click OK to install the two components and restart your computer when the installation has completed.

Now, open a PowerShell console in administrator mode. The first thing to do is to change the execution policy to unrestricted using the following command:

Set-ExecutionPolicy Unrestricted

Then you can install the ContainerImage package provider:

Install-PackageProvider ContainerImage -Force

This package provider will allow you to pull the base operating system image to run Hyper-V containers. In this case, as you are going to run Hyper-V container you need to use the NanoServer base container image. To pull this image, you have to execute the following command:

Install-ContainerImage NanoServer

Depending on your Internet connection, this step can take a while…

Once the base container image is downloaded you can install Docker on your machine to be able to run and manage containers. To do that, you can download a PS script from http://aka.ms/tp5/update-containerhost and save it on your computer. Just run this script that will install all the stuff you need: the Docker client, the Docker deamon, all the configuration, environment variables…

You can now use the Docker commands to work with Hyper-V containers! For example getting the list of available images on your computer:

To be able to use this image without specifying its tag you can tag it as the latest image using the docker tag command:

Now you can switch to a CMD window, with administrator rights and create a new Hyper-V container use the following command:

docker run -it –isolation=hyperv nanoserver cmd

After a few seconds you will be running in an Hyper-V container!

You’re done Smile You can now run any Hyper-V container on your Windows 10 computer. Do you like it?

If you have any question about this post or running containers on Windows, feel free to contact me on Twitter @jcorioland

Julien
Click to expand...

Source: https://blogs.msdn.microsoft.com/jco...ws-10-desktop/

Windows 10: Difference between docker ps and wsl -l -v

Difference between docker ps and wsl -l -v

Difference between docker ps and wsl -l -v

Difference between docker ps and wsl -l -v

Difference between docker ps and wsl -l -v - Similar Threads - Difference between docker

What is the Difference Between Hyper-V and CPU/Hardware Virtualization?

What is the Difference Between Hyper-V and CPU/Hardware Virtualization?

What is the Difference Between Hyper-V and CPU/Hardware Virtualization?

WSL stopped working after uninstall Docker Desktop

WSL stopped working after uninstall Docker Desktop

HYPERVISOR_ERROR, WHEA_UNCORRECTABLE_ERROR with Hyper-V + Docker + WSL2

HYPERVISOR_ERROR, WHEA_UNCORRECTABLE_ERROR with Hyper-V + Docker + WSL2

Windows 365 Cloud PC - Docker and or WSL support

Different D/L speeds