Add azure option (docker#86)

* clean up after Mano

* add sconfig note

* superflous whitespace

* normalize formatting

* Add Azure option, and more cleanup

Author: friism

windows/windows-containers/Setup.md

@@ -1,10 +1,12 @@
-## Setup
-This chapter explores setting up your Windows environment to properly use Windows containers. You have two choices for environment at this point.
+# Setup
+
+This chapter explores setting up a Windows environment to properly use Windows containers. There are three options for running Windows containers:
 
 + Windows 10 with the Anniversary Update
-+ Windows Server 2016
++ Windows Server 2016 on Azure
++ Windows Server 2016 on bare metal or in VM
 
-### Windows 10 with Anniversary Update
+## Windows 10 with Anniversary Update
 
 For developers, Windows 10 is a great place to run Docker Windows containers and containerization support was added to the the Windows 10 kernel with the [Anniversary Update](https://blogs.windows.com/windowsexperience/2016/08/02/how-to-get-the-windows-10-anniversary-update/) (note that container images can only be based on Windows Server Core and Nanoserver, not Windows 10). All that’s missing is the Windows-native Docker Engine and some image base layers.
 
@@ -14,50 +16,74 @@ With the public beta installed, the Docker for Windows tray icon has an option t
 
 ![Image of switching between Linux and Windows development environments](images/docker-for-windows-switch.gif "Image of switching between Linux and Windows development environments")
 
-Switch to Windows containers and skip the next section.
+Switch to Windows containers and skip the next sections.
 
+## Windows Server 2016 on Azure
 
-### Windows Server 2016
+It's very easy to setup a fully configured Microsoft Azure VM with Docker Engine running, and base images pre-loaded:
 
-Windows Server 2016 is the where Docker Windows containers should be deployed for production. For developers planning to do lots of Docker Windows container development, it may also be worth setting up a Windows Server 2016 dev system (in a VM, for example), at least until Windows 10 and Docker for Windows support for Windows containers matures. Running a VM with Windows Server 2016 is also a great way to do Docker Windows container development on macOS and older Windows versions.
+ 1. Create a [Windows Server 2016 Datacenter - with Containers VM](https://azure.microsoft.com/en-us/marketplace/partners/microsoft/windowsserver2016datacenterwithcontainers/). This VM image has Docker pre-installed and the Windows base layers pre-loaded.
+ 2. Select "Classic" deployment model and hit "Create"
+ 3. Input setup parameters. Default settings are good
+ 4. Check the Summary and hit "OK". Setup will take a couple of minutes
+ 5. Once the VM is running, select "Connect" to open a remote desktop connection. If using macOS, get the free [Remote Desktop app in the Mac App Store](https://itunes.apple.com/us/app/microsoft-remote-desktop/id715768417?mt=12).
+ 6. Login with the username and password configured during setup
+ 7. Start PowerShell
+ 8. `Start-Service docker`
+ 9. Check that Docker is running with `docker version`
 
-Once Windows Server 2016 is running, log in, run Windows Update to ensure you have all the latest updates and install the Windows-native Docker Engine directly (that is, not using “Docker for Windows”). You have two options for that:
+![Creating Azure Virtual Machine](images/Azure-ws2016-Create-Virtual-Machine.PNG)
 
-#### Option 1
-GitHub user @PlagueHQ has set-up a [Powershell script](https://www.powershellgallery.com/packages/Install-DockerOnWS2016UsingDSC/1.0.1/DisplayScript "DockerOnWS2016UsingDSC Script") in the Powershell Gallery. You can run it in two steps:
+![Connecting to Azure Virtual Machine](images/Azure-ws2016-Connect.PNG)
 
-```
-Install-Script -Name Install-DockerOnWS2016UsingDSC
-Install-DockerOnWS2016UsingDSC.ps1
-```
+## Windows Server 2016 on bare metal or in VM
+
+Windows Server 2016 is where Docker Windows containers should be deployed for production. For developers planning to do lots of Docker Windows container development, it may also be worth setting up a Windows Server 2016 dev system (in a VM, for example), at least until Windows 10 and Docker for Windows support for Windows containers matures. Running a VM with Windows Server 2016 is also a great way to do Docker Windows container development on macOS and older Windows versions.
+
+Once Windows Server 2016 is running, log in, run Windows Update (use `sconfig` on Windows Server Core) to ensure all the latest updates are installed and install the Windows-native Docker Engine (that is, don't use "Docker for Windows"). There are two options: Install using a Powershell Package (recommended) or with DSC.
+
+### PowerShell Package Provider (recommended)
+
+Microsoft maintains a [PowerShell package provider](https://www.powershellgallery.com/packages/DockerMsftProvider) that lets easily install Docker on Windows Server 2016.
 
-#### Option 2
-To run it in a more manual fashion, you can install it using NuGet. Run the following in an Administrative PowerShell prompt:
+Run the following in an Administrative PowerShell prompt:
 
 ```
-Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
 Install-Module -Name DockerMsftProvider -Force
 Install-Package -Name docker -ProviderName DockerMsftProvider -Force
 Restart-Computer -Force
 ```
 
-Docker Engine is now running as a Windows service, listening on the default Docker named pipe. For development VMs running (for example) in a Hyper-V VM on Windows 10, it might be advantageous to make the Docker Engine running in the Windows Server 2016 VM available to the Windows 10 host:
+### PowerShell Desired State Configuration
+
+If interested in experimenting with [Windows PowerShell Desired State Configuration](https://msdn.microsoft.com/en-us/powershell/dsc/overview), Daniel Scott-Raynsford has built a [prototype script that uses DSC to install Docker Engine](https://www.powershellgallery.com/packages/Install-DockerOnWS2016UsingDSC/1.0.1/DisplayScript). 
+
+Here's how to use it:
 
 ```
-# Open firewall port 2375
-netsh advfirewall firewall add rule name="docker engine" dir=in action=allow protocol=TCP localport=2375
-
-# Configure Docker daemon to listen on both pipe and TCP (replaces docker --register-service invocation above)
-Stop-Service docker
-dockerd --unregister-service
-dockerd -H npipe:// -H 0.0.0.0:2375 --register-service
-Start-Service docker
+Install-Script -Name Install-DockerOnWS2016UsingDSC
+Install-DockerOnWS2016UsingDSC.ps1
 ```
 
+See Daniel's blog post for [details on installing Docker with DCS](https://dscottraynsford.wordpress.com/2016/10/15/install-docker-on-windows-server-2016-using-dsc/).
+
+Whether using the PowerShell Package Provider or DSC, Docker Engine is now running as a Windows service, listening on the default Docker named pipe.
+
+For development VMs running (for example) in a Hyper-V VM on Windows 10, it might be advantageous to make the Docker Engine running in the Windows Server 2016 VM available to the Windows 10 host:
+
+    # Open firewall port 2375
+    netsh advfirewall firewall add rule name="docker engine" dir=in action=allow protocol=TCP localport=2375
+    
+    # Configure Docker daemon to listen on both pipe and TCP (replaces docker --register-service invocation above)
+    Stop-Service docker
+    dockerd --unregister-service
+    dockerd -H npipe:// -H 0.0.0.0:2375 --register-service
+    Start-Service docker
+
 The Windows Server 2016 Docker engine can now be used from the VM host by setting `DOCKER_HOST`:
 `$env:DOCKER_HOST = "<ip-address-of-vm>:2375"`
 
-## Next Steps
+# Next Steps
 See the [Microsoft documentation for more comprehensive instructions](https://msdn.microsoft.com/virtualization/windowscontainers/containers_welcome "Microsoft documentation").
 
 Continue to Step 2: [Getting Started with Windows Containers](WindowsContainers.md "Getting Started with Windows Containers")