dcsimg
December 13, 2017
Hot Topics:

Getting Started with Docker for Windows

  • October 6, 2017
  • By Deepak Vohra
  • Send Email »
  • More Articles »

Docker was made available in 2013; one of the limitations early on had been that Docker did not run on Windows OS. Docker was designed to run on the Linux kernel initially. Multiple Docker containers running in isolation reused the same Linux kernel. Docker was not platform agnostic.

In 2015-2016, Docker for Windows was introduced, first as Beta, to make it feasible to run a Docker daemon on Windows Server 2016. No virtualization is involved to run the Docker daemon on Windows. The Windows Server Containers reuse the host OS kernel and create a sandboxed environment similar to how Docker containers on Linux do. The first stable release of Docker for Windows was made available in July 2016. The Beta release is called Edge, starting with the CE release model. Docker for Windows (Stable and Edge) are supported on Windows 10 and Windows Server 2016. Docker for Windows has the provision to run both Docker Linux containers and Docker Windows containers. In this tutorial, we shall get started with using Docker for Windows on Windows Server 2016.

This tutorial has the following sections:

Setting the Environment

Because Docker for Windows supports only Windows 10 and Windows Server 2016, we need to create an AWS EC2 instance running Windows Server 2016 OS if either of these is not available on a local machine. We have used Windows Server 2016 instance running on AWS EC2. Why Windows Server 2016 and not Windows 10?

  • Windows 10 is designed for the desktop and not designed for the Cloud.
  • Windows 10 is not available on EC2. Windows 10 is available on Microsoft Azure, but not available in the free tier. EC2 instances based on Microsoft Windows Server 2016 with SQL Server 2016 Express AMI are eligible for the free tier.
  • Windows Server 2016 was the first OS to support Docker for Windows

Launch a Windows Server 2016 instance on EC2 with Microsoft Windows Server 2016 with SQL Server 2016 Express AMI, using the procedure discussed in an earlier article, "Setting Up Windows Server 2016 on Amazon EC2."

If you are not familiar with AWS EC2 and are primarily an Azure user, a Windows Server 2016 instance on Azure may be used.

Connect to the Windows Server 2016 instance from a local machine, which is also discussed in the earlier article "Setting Up Windows Server 2016 on Amazon EC2."

Installing Docker for Windows

In this section, we shall install Docker for Windows. Double-click the IE icon, as shown in Figure 1.

Launching IE
Figure 1: Launching IE

Double-click the Get Docker for Windows (Stable) link to download the binaries for Docker for Windows, as shown in Figure 2.

Downloading Docker for Windows binaries
Figure 2: Downloading Docker for Windows binaries

Double-click the Docker for Windows Installer, as shown in Figure 3.

Docker for Windows Installer
Figure 3: Docker for Windows Installer

The Docker for Windows files start to get unpacked (see Figure 4).

Unpacking files
Figure 4: Unpacking files

Docker for Windows starts to get installed, as indicated by the "Installing…" message in Figure 5.

Installing Docker for Windows
Figure 5: Installing Docker for Windows

Docker for Windows gets installed, as shown in Figure 6. Click Close and log out. As a message indicates, the user must log out of Windows to complete the installation.

Docker for Windows installed
Figure 6: Docker for Windows installed

Click Connect in Chrome RDP again to connect to the Windows Server 2016 instance, as shown in Figure 7.

Re-connecting to Windows Server 2016
Figure 7: Re-connecting to Windows Server 2016

The Docker for Windows icon should have been added to the Windows screen (see Figure 8).

Docker for Windows icon
Figure 8: Docker for Windows icon

Starting Docker

To start the Docker daemon, double-click the Docker for Windows icon. As the message in Figure 9 indicates, "Docker is starting…"

Docker is starting
Figure 9: Docker is starting

A dialog prompts with the message that Hyper-V is not enabled. To enable Hyper-V, click OK, as shown in Figure 10.

Enabling Hyper-V
Figure 10: Enabling Hyper-V

The Windows Server 2016 machine restarts and, when the Docker has started running, the message "Docker running…" gets displayed, as shown in Figure 11.

Docker is running
Figure 11: Docker is running

Docker for Windows Settings

To display and modify (if required) the Docker for Windows settings, right-click the Docker icon shown in Figure 11 and select Settings, as shown in Figure 12.

Settings
Figure 12: Settings

The different settings categories—General, Shared Drives, Advanced, Network, Proxies, Daemon, Diagnose & Feedback, and Reset—are provided, as shown in Figure 13. The General settings include the checkboxes Start Docker when you log in, Automatically check for updates, Send usage statistics; all of these are selected by default. The Proxies settings are the proxies Docker uses to pull Docker images. By default, no proxies are configured. With the Daemon settings, the Docker daemon may be configured with some experimental features, which include Insecure registries and registry mirrors. The "Docker is running" message indicates that Docker is running. No settings need to be modified by default.

Docker for Windows settings
Figure 13: Docker for Windows settings

Using the PowerShell

With the Docker daemon running, Docker commands may be used to run Docker Windows containers or the Docker Linux container. By default, the Docker Windows containers may be run, but a feature toggle is provided, as shown in Figure 12, to Switch to Linux Containers. If the Linux containers mode is enabled, the toggle setting becomes Switch to Windows containers, as shown in Figure 14.

Toggle Setting Switch to Windows Containers
Figure 14: Toggle Setting Switch to Windows Containers

Docker commands may be run in a command shell such as cmd.exe or PowerShell. To launch PowerShell, select Windows PowerShell from the Windows Server, as shown in Figure 15.

Launching PowerShell
Figure 15: Launching PowerShell

The PowerShell command line gets launched, as shown in Figure 16.

PowerShell
Figure 16: PowerShell

Listing Docker Version and Info

Run the following command to list the Docker version details:

docker version

The command output includes the Docker Server Version 17.06.2-ce, API Version 1.30, and the Built. The OS/Arch is listed as windows/amd64 (see Figure 17).

Output from docker version
Figure 17: Output from docker version

Run the following command to list just the Docker server version:

docker --version

The Docker server version is 17.06.2-ce, as shown in Figure 18.

Docker Server Version
Figure 18: Docker Server Version

The Docker Compose and Docker Machine versions may also be listed, as shown in Figure 19.

Docker Compose and Machine Versions
Figure 19: Docker Compose and Machine Versions

To list system-wide information, run the following command:

docker info

The system-wide information gets listed, as shown in Figure 20.

The docker info output
Figure 20: The docker info output

Using Docker Commands

The Docker commands may be used to run Docker Windows containers or Docker Linux containers based on the Windows/Linux mode set. The docker run command output in Docker Windows Containers mode is shown in Figure 21.

Output from docker run
Figure 21: Output from docker run

The docker ps command does not list any containers running, as shown in Figure 22.

Output from docker ps
Figure 22: Output from docker ps

Fixing Common Issues

Using Docker for Windows could come across some issues; some of these issues are discussed next. The error "Unable to write to the database. Exit code: 1" could get generated, as shown in Figure 23.

An error message
Figure 23: An error message

If Hyper-V was not enabled when installing Docker for Windows, uninstall and reinstall with Hyper-V enabled (refer to Figure 10).

Restarting Docker might fix an error. To restart, select Reset in Settings and click Restart Docker, as shown in Figure 24.

Restart Docker
Figure 24: Restart Docker

In the Restart Docker dialog, click Restart (see Figure 25).

Restart Docker
Figure 25: Restart Docker

The Docker is restarting message should get displayed, as shown in Figure 26.

Docker is restarting
Figure 26: Docker is restarting

When Docker starts to run, the message "Docker is running" gets displayed, as shown in Figure 27.

Docker is running
Figure 27: Docker is running

If the issue is still not fixed, the Docker for Windows Service listed in Figure 28 might need to be restarted.

Docker for Windows Service
Figure 28: Docker for Windows Service

Right-click Docker for Windows Service and select Restart, as shown in Figure 29.

Restarting Docker for Windows Service
Figure 29: Restarting Docker for Windows Service

If Docker is not running, the docker commands such as docker version and docker info generate an error, as shown in Figure 30.

The docker version command generates an error message
Figure 30: The docker version command generates an error message

Conclusion

In this tutorial, we discussed getting started with Docker for Windows on Windows Server 2016. Docker for Windows is also supported on Windows 10. Docker for Windows runs both Windows containers and Linux containers.






Comment and Contribute

 


(Maximum characters: 1200). You have characters left.

 

 


Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Sitemap | Contact Us

Thanks for your registration, follow us on our social networks to keep up-to-date