Tag: Hyper-V Container

Jun022018June 2, 2018August 27, 20180Commentby Thomas Maurer
Windows Server Banner

Microsoft Windows Server Summit – Online Summit

Posted in Cloud, Containers, Hyper-V, Microsoft, Microsoft Azure, Microsoft Azure Stack, Virtualization, Windows Server, Windows Server 2016, Windows Server 2019, Work

On Tuesday, June 26, 2018 Microsoft will held the Windows Server Summit Online, a virtual experience to learn tips and tricks for modernizing your infrastructure and applications—regardless of whether you’re running it on-premises or in the cloud. And you can bet you will also get some new information on Windows Server 2019.

Learn how to build the future with Windows Server

Microsoft will talk about the roadmap for Windows Server, and let you discover new skills and best practices, and get your questions answered in conversations with the Microsoft experts behind our products.

This online summit will focus on 4 key areas of Windows Server:

  • Hybrid – Learn how Windows Server helps you integrate Azure services into your on-premises environment and how to better run Windows Server in Azure.
  • Security – Better security starts with the Operating System. Learn how Windows Server helps you elevate your company’s security posture.
  • Hyper-converged infrastructure (HCI) – Windows Server 2016 introduced new HCI capabilities that are game-changers. Now, check what’s new around HCI for Windows Server 2019.
  • Application platform – Containers are changing the way developers and operations teams run applications. Learn how Windows Server helps you modernize yours.

So if you want to know more, join the Microsoft online event!

 


Oct272017October 27, 2017August 24, 20180Commentby Thomas Maurer
Docker Windows Server Container Images

Docker Container Images for Windows Server 1709 and new tagging

Posted in Cloud, Containers, Docker, Hyper-V, Microsoft, Microsoft Azure, Microsoft Azure Stack, Nano Server, PowerShell, Server Core, Virtualization, Web, Windows, Windows 10, Windows Server, Windows Server 1709, Windows Server 2016, Work

Last week Microsoft announced new Windows Server 1709 and the new Windows Server 1709 container images. The new container images in Windows Server version 1709 are highly optimized, especially in size. So for example the new Nano Server Container Image in 1709 is 5x smaller than the Nano Server Container Image in Windows Server 2016.

Microsoft also made some changes to tagging which is interesting.

If you want to use the latest images of the container images based on the Windows Server 2016 (which is in the Long-Term Servicing Channel, LTSC) you just run:

 
"microsoft/nanoserver"
or
"microsoft/windowsservercore"

This will give you the latest images of the Windows Server and Nano server container images. If you want to run a specific patch level of the Windows Server 2016 (LTSC)m images, you can run the following:

 
"microsoft/nanoserver:10.0.14393.1770"
or
"microsoft/windowsservercore:10.0.14393.1770"

Docker Windows Server Container Images Size

If you want to use the new Windows Server 1709 container images from the Semi-Annual Channel you can run the following

 
"microsoft/nanoserver:1709"
or
"microsoft/windowsservercore:1709"

and again you cans also add a specific base OS container image by using a KB number:

 
"microsoft/nanoserver:1709_KB4043961"
or
"microsoft/windowsservercore:1709_KB4043961"

If you already tried out the new container images during the development using the insider images, they still existing:

 
"microsoft/nanoserver-insider"
or
"microsoft/windowsservercore-insider"

However, I am not sure what the plan for the insider images is going forward.


Oct242017October 24, 2017August 27, 20187Commentsby Thomas Maurer
Docker for Windows Update Linux Containers

How to run Docker Linux Container on Windows 10 Fall Creator Update

Posted in Cloud, Containers, Docker, Hyper-V, Microsoft, Microsoft Azure, Virtualization, Web, Windows, Windows 10, Windows Server, Work

I just blogged about how to run a Docker Linux Container natively on the new Windows Server version 1709. Docker today released a new update for Docker on Windows which also enables this scenario a little bit easier on your Windows 10 machine. It will ask you if you want to use the new feature to run Linux Containers natively on a Hyper-V Container running on Windows 10 (without the Moby VM).

As you can see the only thing right now you have to turn the feature on and off, since in this technical preview it is not yet possible to run Linux and Windows containers in parallel. But I guess soon that will be the case.

What you need is:

  • Windows 10 Fall Creators Update (Build 16299, Version 1709, RS3)
  • Docker for Windows 17.10.0-ce-win36 (13788) or higher

Enable Linux Containers on Windows

You can change the settings in the Docker Settings:

Docker for Windows Settings Enable Linux contianers on Windows

With hat setting on you can now run Linux Containers such as ubuntu on Windows directly, without having a Linux Virutal Machine running in the background to host the Linux containers.

Docker Run Ubuntu on Windows 10 Verions

Now you can also do some other fancy things like run the Azure CLI in a Linux Container on Windows 10.

Docker Azure CLI on Linux on Windows 10 Container

Simple and effective, and it will be even more powerful when you can run Linux and Windows Container in parallel on Windows Sever and on Windows 10.


Oct242017October 24, 2017August 24, 20186Commentsby Thomas Maurer

How to run Docker Linux Container on Windows Server 1709

Posted in Cloud, Containers, Hyper-V, Microsoft, Microsoft Azure, Microsoft Azure Stack, Nano Server, PowerShell, Private Cloud, Server Core, Virtualization, Web, Windows, Windows 10, Windows Server, Windows Server 2016, Work

As mentioned Microsoft released the final version of Windows Server 1709 in the last week. Windows Server 1709 brings a couple of new improvements, especially in the container space. Microsoft and Docker are working on bringing Linux Container support to Windows Server, so you can now run Windows and Linux Container at the same time on a Windows Server Container Host running Windows Server 1709 or Windows 10 with the Fall Creators Update (1709).

In this post I want to show you how you setup up a Container Host to run Windows and Linux Containers at the same time using Docker.

Create Container Host Virtual Machine

Enable Nested Virtualization

If you run Docker on a physical server you can skip this step. If you want to run Docker Containers using Linux inside a Virtual Machine running on Hyper-V you should enable Nested Virtualization for the Container Host Virtual Machine. You can do this by running the following command:

 
Get-VM *WinContainerHost* | Set-VMProcessor -ExposeVirtualizationExtensions $true

if you want to do this on a Hyper-V Server in Azure, check out this post: How to setup Nested Virtualization in Microsoft Azure

Install Docker Enterprise Edition Preview on Windows Server 1709

First you have to install Docker Enterprise Edition Preview on your Windows Server 1709 container host. You can install the Docker EE preview using PowerShell package management, using the following commands:

 
Install-Module DockerProvider
Install-Package Docker -ProviderName DockerProvider -RequiredVersion preview

As mentioned this is a preview version of Docker EE which enables a bunch of new features, to run Docker in production environments please use Docker EE 17.06.

Enable Docker Linux Containers on Windows

The preview Docker EE package includes a full LinuxKit system (13MB) for use when running Docker Linux containers. To enable this use the following command:

 
[Environment]::SetEnvironmentVariable("LCOW_SUPPORTED", "1", "Machine")
Restart-Service Docker

to disable it again use the following:

 
[Environment]::SetEnvironmentVariable("LCOW_SUPPORTED", $null, "Machine")
Restart-Service Docker

Run Docker Linux Container on Windows Server

Docker Ubuntu Container on Windows Server

Now you are able to run Linux Containers on Windows Server 1709.

 
docker run ubuntu

for fun you can also run Nyancat!

Docker Nyan Cat on Windows Server

 
docker run -it supertest2014/nyan

Things are still in preview, so don’t expect to work 100% :)


May152017May 15, 2017September 1, 20187Commentsby Thomas Maurer
Azure Nested Virtualization

Hyper-V Container and Nested Virtualization in Microsoft Azure Virtual Machines

Posted in Cloud, Containers, Hyper-V, Microsoft, Microsoft Azure, Microsoft Azure Stack, Nano Server, PowerShell, Private Cloud, Virtualization, Windows, Windows 10, Windows Server, Windows Server 2016, Work

Last week Microsoft announced some pretty cool new Azure Stuff, like the Azure Cloud Shell, Azure PowerShell 4.0, Azure Cosmos DB and much more. In the session about Azure Compute, Microsoft introduced a bunch of new features, like new VM sizes, new experiences and new integration technology as well as updates to Azure Service Fabric, Azure Container Service and Azure Functions. One which really got my interest was the announcement about the new Virtual Machines sizes for Dv3 and Ev3, which will enable customers to use Virtualization inside their Windows Server Virtual Machines on Azure, enabled by Nested Virtualization from Windows Server 2016 Hyper-V. With that Dv3 and Ev3 Azure Virtual Machines are Nested Virtualization enabled. This means you can now run Nested Virtualization in Microsoft Azure Virtual Machines.

Update: The new Azure Dv3 and Ev3 VM sizes are now available, and you can now use Nested Virtualization in Azure.

Azure Nested Virtualization and Hyper-V Containers

You can now run Hyper-V in Azure Virtual Machines and even more important you can now run Hyper-V Container inside Azure Virtual Machines. With the announcements for Windows Server 2016 supporting Hyper-V Containers running Linux and Windows Server this is great news. You will be able to create Container Hosts in Azure running Windows Server and create Windows and Linux Containers on the same Container Host.

Azure VM Sizes

By the way, if you want to run Hyper-V Container in Azure today, and you don’t want to wait until the Dv3 and Ev3 series are available you can run them inside Azure Service Fabric. So yes, Microsoft now allows you to run Hyper-V Containers in Azure Service Fabric.

Azure Nested Virtualization Demo

As you could see in the demo, they are offering quite large Virtual Machines with a lot of RAM, running on Intels Xeon E7 CPUs.


Jun272016June 27, 2016June 27, 20160Commentby Thomas Maurer
VCNRW Nano Server and Container

Video: VCNRW – Virtualization Community NRW recording about Nano Server and Windows Containers

Posted in Cloud, Containers, Events, Hyper-V, Microsoft, Nano Server, PowerShell, Private Cloud, Server Core, Virtualization, Web, Windows, Windows 10, Windows Server, Windows Server 2016, Work

A couple of weeks ago I had the chance to speak at the VCNRW – Virtualization Community NRW community event at the Microsoft Offices in Cologne. The recording of this session (in German) is now available on Microsoft Channel 9.

Nano Server and Containers (on Microsoft Channel 9)

Have a look at the latest Cloud Technologies from Microsoft. Learn about the next Microsoft Cloud Platform Server called Nano Server and Windows Containers. Both solutions are built for the future and will fundamentally change how we do IT. Learn why we need Nano Server and Windows Containers and how we deploy, manage and operate them.


Feb012016February 1, 2016November 1, 20180Commentby Thomas Maurer
Switch Windows Container to Hyper-V Container

Switch a Windows Server Container to a Hyper-V Container

Posted in Cloud, Containers, Hyper-V, Microsoft, Nano Server, PowerShell, Virtualization, Web, Windows, Windows 10, Windows Server, Windows Server 2016, Work

With Technical Preview 4 of Windows Server 2016 made the new Hyper-V Containers available. With that you can now use Windows Server Container and Hyper-V Container. To run Hyper-V Containers you have to make sure, you have Hyper-V Nested Virtualization active for your Container Host VM.

If you create a new Container it will create a Windows Server Container by default, if you want to create a Hyper-V container you have to switch the RuntimeType to Hyper-V.

With the following command you can see which RuntimeType the Container has:

 
Get-Container MyContainer01 | select Name, State, RuntimeType

To change the runtime Type to Hyper-V Container you can use the following command:

 
Get-Container MyContainer01 | Set-Container -RuntimeType HyperV

So switch it back to a Windows Server Container you can use the following command:

 
Get-Container MyContainer01 | Set-Container -runtimetype Default

 



  • Follow Me

  • About

    Thomas Maurer

    My name is Thomas Maurer. I am a Senior Cloud Advocate at Microsoft. I am part of the Azure engineering team (Cloud + AI) and engage with the community and customers around the world. I am located in Switzerland. I am focusing on Microsoft technologies, especially cloud and datacenter solutions based on Microsoft Azure, Azure Stack and Windows Server. Opinions are my own.

  • Sponsor

  • Sponsor

    Starwind Virtual SAN

  • Sponsor

    Vembu BDR Suite

  • Sponsor

    Altaro Ad