Book Image

Docker on Windows - Second Edition

By : Elton Stoneman
Book Image

Docker on Windows - Second Edition

By: Elton Stoneman

Overview of this book

Docker on Windows, Second Edition teaches you all you need to know about Docker on Windows, from the 101 to running highly-available workloads in production. You’ll be guided through a Docker journey, starting with the key concepts and simple examples of .NET Framework and .NET Core apps in Docker containers on Windows. Then you’ll learn how to use Docker to modernize the architecture and development of traditional ASP.NET and SQL Server apps. The examples show you how to break up legacy monolithic applications into distributed apps and deploy them to a clustered environment in the cloud, using the exact same artifacts you use to run them locally. You’ll see how to build a CI/CD pipeline which uses Docker to compile, package, test and deploy your applications. To help you move confidently to production, you’ll learn about Docker security, and the management and support options. The book finishes with guidance on getting started with Docker in your own projects. You’ll walk through some real-world case studies for Docker implementations, from small-scale on-premises apps to very large-scale apps running on Azure.
Table of Contents (18 chapters)
Free Chapter
1
Section 1: Understanding Docker and Windows Containers
6
Section 2: Designing and Building Containerized Solutions
10
Section 3: Preparing for Docker in Production
14
Section 4: Getting Started on Your Container Journey

Defining applications with Docker Compose

The Docker Compose file format is very simple. YAML is a human-readable markup language, and the Compose file specification captures your application configuration, using the same option names that the Docker CLI uses. In the Compose file, you define the services, networks, and volumes that make up your application. Networks and volumes are the same concepts that you use with the Docker engine. Services are an abstraction over containers.

A container is a single instance of a component, which could be anything from a web app to a message handler. A service can be multiple instances of the same component running in different containers, all using the same Docker image and the same runtime options. You could have three containers in the service used for your web application and two containers in the service you use for a message handler...