Skip to main content

Docker on Windows - Part 1 Installation & Configuration

As we go through the journey of distributed applications and containers, there's an up-and-comer, Microsoft. Microsoft has been in the container game since Server 2016, and it is now available on Windows 10.

In this blog post, we're going to go over the configuration with PowerShell, Chocolatey, and Docker. First things first, lets confirm you have chocolatey installed. Chocolatey is a package manager, like brew, yum, or aptitude. To install Chocolatey, open up a PowerShell prompt as an administrator and run the following:

Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

This does the following:
1. Sets an execution policy to bypass for this installation
2. Forces the installations, which means no prompts
3. Utilizes a .NET object System.Net.WebClient to make an API call to Chocolatey.

Now that this is installation, let's confirm by running 'choco'. You should see a similar output as below:

PS C:\WINDOWS\system32> choco 
Chocolatey v0.10.11 
Please run 'choco -?' or 'choco -?' for help menu.

Next, we're going to install the Docker CLI so we can utilize the API. Run the following:

choco install docker

 You should see something like the below screenshot.



Confirm Docker installed successfully by simply running docker --version  and you'll see your version number. Please note: Your version may be different than mine.



Now that we have the Docker CLI installed, we need to download Docker for Windows. Please visit https://docs.docker.com/docker-for-windows/install/ and sign up for a free account. Once you do that, you'll be able to continue.


Click on the "Get Docker" button as shown above and it'll start the .EXE. Once completed, go ahead and open that up. You should see a similar window as below.



For the purposes of this blog, feel free to not check "Use Windows containers instead of Linux containers (this can be changed after installation".

Once complete, go ahead and search for Docker, then open. It'll take a short while to get the services up and running.

Go ahead and run get-service *docker* in a PowerShell window to confirm the service is running successfully. 



To confirm that Docker is successfully running, open up a PowerShell prompt and run docker run hello-world and you should see something very similar to the below screenshot:


That's it for this tutorial! Feel free to of course play around and test (in fact, I encourage it). Up next is running a container with Docker on Windows and Docker Compose!

Comments

Popular posts from this blog

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …

Running PowerShell commands in a Dockerfile

As Docker continues to grow we are starting to see the containerization engine more and more on Windows. With the need for containers on Windows, we also need the same automation we get in Linux with Dockerfiles. Today we're going to create a Dockerfile that runs PowerShell cmdlets.
Prerequisites; 1. Docker for Windows
2. A code editor (VSCode preferred)

Let's go ahead and get our Dockerfile set up. Below is the Dockerfile I used for this post.

from mcr.microsoft.com/windows/servercore:1903 MAINTAINER Michael Levan RUN powershell -Command Install-WindowsFeature -Name Web-Server RUN powershell -Command New-Item -Type File -Path C:\ -Name config
As you can see from the above, this is a tiny Dockerfile. What this will do is install the IIS Windows 

Feature and create a new file in C:\ called "config".
You should see something very similar to the below screenshot;

Next let's create a running container out of our image. First we'll need to run docker container ls to

 get o…

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…