Edit: I wrote this article when examining containers on Windows Nano Server TP3 – which wasn’t in a working state. I have not yet had a chance to fully examine containers on Windows Nano Server TP4, but when I get a spare day hours I will no doubt deep dive into it.
If you’re looking for instructions on installing and using containers on Windows Nano Server TP4, start here.
These instructions are more focused on setting up a container host on Windows Server Core TP4, but I have managed to get them working on Windows Nano Server TP4 just fine:
I do plan to document this process over the next week or so.
You’d be forgiven for believing that it was just a simple click of a button (or addition of a package) to get Docker Containers working on a shiny new Windows Nano Server TP3 install. That is what I thought too. But after careful examination of the available documentation I found that there isn’t much information on running actually getting containers working on Nano Server. Sure, there is lots of information on running it on a full or core version of WIndows Server TP3, but Nano is lacking. So, because I’m a bit obsessive I decided I’d have a try and adapting the standard installation process.
Edit: Initially I had a bit of success, but I’ve run into some rather stop dead issues that I haven’t been able to resolve (see later on in this post).
I have continued the investigation here with a much more in depth look at the issues.
tl;dr: Containers on Windows Server Nano 2016 TP3 does not work yet! The Base OS WIM file for Windows Server Nano is required, but has not been provided.
Problems with the Standard Containers Install Script
First up I grabbed a copy of this script from Microsoft which is what is used to install containers on a full Windows Server 2016 install. I took a look at it and identified the things that wouldn’t work on a Nano Server 2016 install. This is what I found:
- The script can optionally configure a NAT switch – this requires the NetNat PS module which isn’t available on Nano.
- The script will install a VM Switch – therefore the Compute package is required to be installed on the Nano Server (the Compute package contains the Hyper-V components).
- The script can download various files from the internet (using the alias wget). Wget and Invoke-WebRequest are not available on Nano Server – so we’ll need to download the files to another machine and pre-copy them to the Nano Server.
- The Expand-Archive is used to extract the NSSM executable, but this cmdlet is not available on Nano Server either – so we’ll need to extract the NSSM.exe on another machine and copy it to the server.
The Process of Installing a Container Host
The process of actually installing a Container Host in Windows Nano Server is as follows:
- Create a Nano Server VHDx with the packages Guest, OEM-Drivers, Compute and Containers.
- Create a new VM booting from the VHDx – this is our Container Host.
- Upload a Base OS WIM file to the Container Host containing that will be used to create new containers.
- Upload Docker.exe to c:\windows\system32\ on the Container Host.
- Upload NSSM.exe to c:\windows\system32\ on the Container Host – this is used to create and run the Docker Service.
- Run the installation script on the Container Host – this will install the networking components and configure the Docker service as well as create the container OS image.
- Create a Container!
In theory the Container Host is now ready to go!
What is Required to build a Nano Server Container Host
A bit of experience with PowerShell is a good help here!
So, to create a Nano Server Container Host you’ll need a few things:
- A machine that can run Generation 2 Hyper-V machines (Gen 1 will probably work but I’m using Gen 2) – this will host your Nano Server. This machine must also be running PowerShell 5.0 (I’m using some PS5.0 only cmdlets)!
- A copy of the Windows Server 2016 TP 3 ISO from here.
- A working folder (I used D:\Temp) where you’ll put all the scripts and other files etc.
- The scripts (I’ll provide them all in a zip file), but they are:
- New-ContainerHostNano.ps1 – this will do everything and is the only script you’ll run.
- Install-ContainerHostNano.ps1 – this is the script that gets automatically run on the Container Host. It is a version of the Microsoft one from here that I have adjusted to work with Nano Server.
- New-NanoServerVHD.ps1 – this is a script I wrote a while back to create Nano Server VHDx files (see this post for more details).
- Convert-WindowsImage.ps1 – this script is required by New-NanoServerVHD.ps1 and is available on Microsoft Script Center.
How Can I use all This?
I haven’t really finished implementing or testing these scripts and I am encountering a problem creating the VM Switch on the Nano Server, but if you’re interested you can get a hold of the scripts in my GitHub repository.
To use them:
- Create a working folder (I used d:\temp).
- Download the four PS1 scripts from the GitHub repository to the working folder.
- Download the Windows Server 2016 TP3 ISO from here and put it in the working folder.
- Download the Base OS Container Image from here (3.5GB download) and put it in the working folder.
- Edit the New-ContainerHostNano.ps1 file in the working folder and customize the variables at the top to suit your paths and such – fairly self explanatory.
- In an Administrative PowerShell run the New-ContainerHostNano.ps1 file.
Please note: This is a work in progress. There are definitely some bugs in it:
- An error is occurring when trying to create the VM Switch in DHCP mode or NAT mode.
- If using NAT mode the NAT module isn’t included in Nano Server so although the VM switch gets created the NAT Network adapter can’t be created.
- NSSM isn’t creating the Docker Service – which may just be an issue with running the PowerShell installation script remotely.
None of the above will stop containers being created though. The containers might not be able to communicate with the world via networking and the Docker management engine might not work, but in theory the containers should still work (at least that is my understanding).
The BIG Problem
Any container that you create requires a WIM file that contains the container base OS image that container will use. Microsoft has so far only provided a base WIM file for WIndows Server 2016 Core installations – they haven’t provided a container base OS Image for Windows Server 2016 Nano yet. You can download the Core one from here (3.5GB download).
If you try to use the NanoServer.WIM file from the Windows Server 2016 ISO as the container base OS image you can’t even create the container at all.
I did try putting the Core WIM file downloaded above onto the Nano Server. I could then create a container OK, but an error would occur starting it up:
Update 2015-10-29: There is a new video available online from Microsoft of Mark Russinovich (Azure CTO) doing a container demonstration using a Nano Server. It clearly shows that the NanoServer Base Container Image does exist. So perhaps we’ll see this in the TP4 release.
The video can be seen here.
Feel free to let me know if you can solve any of these issues! Any help is appreciated. I’ll continue to work on this and post any additional results.