Docker – Hyper-V Containers are going to allow running of Linux Containers

containersdockerhyper-vwindows-server-2016

I cannot find a definitive answer anywhere (lots of contradicting information and very general). With the new version of MS Windows Server 2016 it's going to be possible to run containers in two modes:

Windows Container
Hyper-V Container

First one (windows container) is a classic container which shares the same MS Windows Server kernel and not very secure. However second (hyper-v container) uses hypervisor to provide isolation and security.

Sine release of Windows 10 Anniversary Update few months back Microsoft has included “Windows Subsystem for Linux”.

Is it going to be possible to run Linux (Ubuntu, Debian, CoreOS, etc. ?) containers using the Hyper-V Container technology ?

I have searched everywhere but cannot find an container image with Linux for Hyper-V Containers. Only two available which I'm able to find are Nano Server and Windows Server 2016 which are provided by Microsoft.

Using Technical Preview 5 (TP5) of Windows Server 2016 now, the general availability (GA) is going to be any day soon as announced at Ignite conference few days back.

Anybody got any news ? able to verify ?

Best Answer

Linux Containers on Windows (lcow) now is available on Windows Server, version 1709. https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers.

I have created a blog post regarding to this topic here: https://chunliu.me/2018/02/12/running-linux-containers-on-windows-server-2016/. Hope it helps.

Related Solutions

How to add the SMTP Server role in Nano Server

It is early days for Nano Servers. What we have right now is an early preview and only a very limited number of features is supported. IIS and SMTP are not among them.

Get-WindowsFeature is from the Server Manager module which is not enabled on Nano

dism.exe -online -get-features -format:table

you get something like:

------------------------------------- | --------
Feature Name                          | State
------------------------------------- | --------
ServerManager-Core-RSAT               | Disabled
ServerManager-Core-RSAT-Role-Tools    | Disabled
ServerManager-Core-RSAT-Feature-Tools | Disabled
FileAndStorage-Services               | Enabled
Storage-Services                      | Enabled
File-Services                         | Enabled
CoreFileServer                        | Enabled
File-Services-Search-Service          | Disabled
Dedup-Core                            | Disabled
SmbDirect                             | Enabled
Microsoft-Hyper-V                     | Enabled
FailoverCluster-NanoServer            | Enabled
SmbWitness                            | Disabled
Storage-Replica                       | Disabled

You can use Enable-WindowsOptionalFeature to enable some, but that doesn't really help.

As long as we don't have any additional packages we can not add more features to the server.

Hyper-V VM – Cannot Access Internet with DHCP but Can With Static

There is not so much moving parts here: type of your network adapter, connectivity type assigned for VM and IP configuration are the main parts.

Are you sure static IP config is valid and complete (default gateway etc.)?
Are you sure there is no duplicate IPs in your network?
Are you sure that your VM adapater has default gateway specified?
Have you tried explicitly ping using IPv4 or IPv6?
Does ping 127.0.0.1 / ::1 works fine?

See very similar question: https://superuser.com/questions/662105/no-internet-access-when-using-static-ip There root cause was missing default gateway.

If I were you I would try to read VM's NIC and then try the same static IP config (providing it is valid one) - may well fix your issue too.

Beyond that it could be something more obscure with more difficult fix. Example: https://thommck.wordpress.com/2010/11/04/fixing-a-failed-hyper-v-guest-network-adapter/

General troubleshooting approach to "PING: Transmit failed. General Failure - Reasons and Solution" error: http://www.corenetworkz.com/2011/08/ping-transmit-failed-general-failure.html

Related Topic