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

Starting a multi-container solution

As you make more use of Docker, your solution will become distributed across more containers—either running custom code that you split out from a monolith or tried and trusted third-party software from Docker Hub or a third-party registry.

NerdDinner now runs across five containers—SQL Server, the original web app, the new homepage, the NATS message queue, and the message handler. There are dependencies between the containers, and they need to be started in the correct order and created with the correct names so that components can be found using Docker's service discovery.

In the next chapter, I'll use Docker Compose to declaratively map out these dependencies. For now, I have a PowerShell script called ch05-run-nerd-dinner_part-1.ps1 that explicitly starts the containers with the correct configuration:

docker container...