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

Creating a swarm and managing nodes

Docker Swarm mode uses a manager-worker architecture with high availability for managers and workers. Managers are administrator-facing, and you use the active manager to manage the cluster and the resources running on the cluster. Workers are user-facing, and they run the containers for your application services.

Swarm managers can also run containers for your applications, which is unusual in manager-worker architectures. The overhead of managing a small swarm is relatively low, so if you have 10 nodes and 3 are managers, the managers can also run a share of the application workload (but in production you need to be aware of the risks of starving your managers of compute if you're running lots of application workloads on them).

You can have a mixture of Windows and Linux nodes in the same swarm, which is a great way to manage mixed workloads...