Hyper-V support in Windows

[damian123]

Please make it possible to to use hyper-v virtual machines in the Windows build environment.

This will enable to run:

• Docker containers based on other versions of Windows
  • note that the current (as of this writing) Server 1809 version is already missing from the table at Windows container version compatibility | Microsoft Learn. In particular, containes for newer technologies, e.g. Azure Cosmos DB emulator, are not available for 1809
• Linux containers via Chocolatey Software | docker-machine 0.16.2

---

Related topics:

Server 2019 Support with LCOW enabled

One of the most interesting scenarios going forward on Windows is the ability to run Linux and Windows containers side-by-side. This requires a few things: Windows 10 Build 1709 or greater OR Windows Server 2019 The Hyper-V and Containers features installed in Windows (which in turn requires nested virtualization enabled in your VM infrastructure) A docker nightly build with experimental features enabled The LCOW image It would be awesome to see a CI setup available that can host containers l…

Docker Linux containers on Windows

@native-api doesn’t look like Choclatey can help here. Even when installing Docker via Choclatey, pulling down Debian gives me: $ docker pull debian/latest … “image operating system “Linux” cannot be used on this platform” Maybe an option in .travis.yml to flip the VM engine to Linux container mode would fix this.

Running Azure Cosmos DB Emulator docker image

From the instructions for Linux and MacOS in that article, it looks like the emulator itself only exists for Windows – it just can interact with another app running in Linux or MacOS over a network. Docker is available in the Windows build environment but there’s no nested virtualization in it (last time I checked) so the container’s kernel must match the VM’s kernel – i.e. Windows Server 1809.

[StefanScherer]

Thanks for preinstalling Docker on your Windows build agents! Docker Captains approved

Currently only Windows Server, version 1803 is supported. Which is a fine starting point.

Are there plans to provide a broader range of OS versions?
Do you plan to add Hyper-V support to run containers in hyperv isolatation?

When someone wants to provide Windows images for all Windows versions (2016, 1709, 1803, 1809 or 2019) there would be two ways:

1. use the latests Windows Server OS (this would be 2019 or 1809) and build all image variants from here. This would require Hyper-V to build and run older Windows images (2016, 1709, 1803) on the Windows Server 2019 host.

2. provide all Windows Server machines and create a build matrix for 2016, 1709, 1803, 2019. Can we run a step after that matrix to create a manifest-list with docker manifest create or the manifest-tool?

I’ve tried to run older images with hyperv isolation, but this build https://travis-ci.org/StefanScherer/travis-windows-test/builds/477697367 shows me that Hyper-V is not installed.

My .travis.yml for that build is

os: windows
language: bash
services: docker

script:
  - docker version
  - docker images
  - docker info
  - docker run mcr.microsoft.com/windows/nanoserver:1803 ipconfig
  - docker run --isolation hyperv mcr.microsoft.com/windows/nanoserver:1709 ipconfig
  - docker run --isolation hyperv mcr.microsoft.com/windows/nanoserver:sac2016 ipconfig