book

Mastering Docker on Windows

Name: Mastering Docker on Windows
Author: Michael D. Smith
ISBN: 9781836640516

by Michael D. Smith

December 2025

Intermediate to advanced

490 pages

10h 52m

English

Packt Publishing

Read now

Unlock full access

Preface
Free Benefits with Your Book
Part 1: Getting Started with Docker on Windows 11
Chapter 1: Installing and Managing Docker on Windows 11
Technical requirementsDocker overviewSo, what is Docker?Why containers and not just virtual machines?How does Docker work on Windows 11?What you'll need (system requirements)Hardware and performanceInstalling WSL 2 on Windows 11Installing Docker DesktopWhere to download Docker DesktopInstallationPost-installation configurationVerifying Docker installationConfiguring resource limitsCustomizing behavior and startupTroubleshooting some common post-installation issuesEssential Docker commandsPulling an image from Docker HubRunning a containerQuick one-linersGiving containers a nameRunning containers in the backgroundWant to see what's running?Accessing services on a specific portClean runs with --rmManaging Docker images and containersListing running containersInspecting container detailsStopping and removing containersWorking with imagesDangling imagesReusing containersTagging and retagging imagesContainers versus imagesDockerfile basics and image optimizationWhat is a Dockerfile?FROM – Picking your base imageWORKDIR – Setting your working directoryCOPY – Bringing in your application filesRUN – Executing setup commandsCMD – Defining the default commandA basic DockerfileUnderstanding Docker layers and cachingBest practices for clean DockerfilesWhen to use multi-stage buildsDocker image workflow: From build to pushSummary
Chapter 2: Implementing Docker Networking on Windows 11
Technical requirementsUnderstanding Docker networkingWhy networking matters in containersThe default networks in DockerHow Docker handles name resolutionViewing network interfaces from inside a containerHow Docker chooses subnets and addressesListing available driversCreating bridge networks on WindowsWhat makes a bridge network useful?Creating a user-defined bridge networkName resolution and DNSAttaching containers to your bridge networkCustomizing your bridge networkCleaning up networksConfiguring host networks for containersWhat does host networking actually do?Running a container with host networkingCleaning upWhen not to use host networkingSecure networking with overlay networksWhy overlay networks existCreating a secure overlay networkRunning multiple services securelyCleaning upUnderstanding the security trade-offsManaging network security for containersAlways ask, "Can I see it?"Common DNS issues and how to fix themNo DNS? Try IPsVerifying port bindingsFirewall and antivirus interferenceDocker Swarm DNS odditiesMisbehaving networks: Prune and rebuildBest practices for securing Docker networksWindows networking exampleThe Big Lab: Notes serviceSummary
Chapter 3: Managing Docker Volumes and Data Persistence
Technical requirementsOverview of persistent data managementUnderstanding the basicsChoosing the right volume typeIntegrating persistent data into complex workflowsBackup and recovery strategiesSecuring persistent dataImplementing and optimizing volume usage in complex workflowsUsing named volumes for modular workflowsCombining bind mounts with named volumesOptimizing volume mount pointsShared volumes for read-heavy workloadsReplication strategies for write-heavy workloadsCaching build artifactsTesting persistent data scenariosMonitoring and optimizing volume usageVolume pruningMonitoring disk usageProfile volume performanceAdvanced backup and recovery solutions for Docker volumesUnderstanding Docker volume backup optionsAutomating volume backupsScheduling backups with cron jobsUsing backup tools with Docker integrationRecovery strategiesCross-container data sharing strategies for enterprise useUnderstanding cross-container data sharingImplementing advanced sharing scenariosOptimizing performance in data sharingSecurity and troubleshootingRoot cause analysis and fixes for volume management issuesRoot cause analysis techniquesFixes for common volume issuesProactive measures for volume managementThe Big Lab: Adding persistence to the Notes serviceSummary
Part 2: Advanced Docker Techniques on Windows
Chapter 4: Orchestrating Multi-Container Applications with Docker Compose
Technical requirementsUnderstanding Docker ComposeWhat is Docker Compose?The structure of a Compose fileNamed projects and directoriesWhere Compose files belongUseful Compose commands you'll actually useScaling services with Docker ComposeDefining multi-container environmentsWhy multi-container definitions matterBuilding a Compose file with multiple servicesGoing beyond the default networkNamed networksService aliasingConnecting a service to multiple networksRunning Docker Compose applications on WindowsWhere Docker Compose runs on WindowsTroubleshooting common issuesChecking the logsListing running services and their portsRestarting and rebuilding servicesWhen localhost failsStopping and cleaning upChecking network status and connectivityHandling file permission issuesPerformance and permission gotchas on WindowsPractical tuning that actually helpsManaging dependencies with ComposeUnderstanding service dependenciesUsing health checksUsing wait-for scriptsUsing third-party toolsManaging inter-service timing on WindowsDebugging stubborn dependenciesBuilding in retries and graceful failureBest practices for multi-container orchestrationUse explicit service namesAvoid using latest tags in production-like stacksUse named volumesKeep environment variables in a separate .env fileStructure your Compose files clearlyKeep your services leanUse health checksKeep cleanup simpleCheck network behavior regularlyDocument the stack for other developersA more realistic multi-service stackThe Big Lab: Turning the Notes service into a real multi-container stackSummary
Chapter 5: Docker Security and Best Practices on Windows
Technical requirementsUnderstanding Docker securityDocker's security modelWhere things start to get riskyContainers do not equal security by defaultManaging user access and permissionsWhy user access mattersDefining users in DockerfilesAvoiding --privileged and the Docker socketSafer alternatives to mounting the Docker socketManaging file permissionsChecking who a container is running asSecuring Docker images and containersWhy your base image mattersHardening and scanning containersLimiting what a container can doBuild once, run safely anywhereImplementing isolation with namespacesUnderstanding Docker namespacesUsing namespace flags in practiceUsing user namespaces for stronger isolationLimiting host access with namespace isolationMonitoring security and auditing containersWhy visibility mattersAuditing with Docker's built-in toolsAdvanced security and scanning toolsMonitoring in Windows environmentsThe Big Lab: Hardening the Notes serviceSummary
Chapter 6: Optimizing Docker for Performance on Windows
Technical requirementsResource allocation for Docker on WindowsHow Docker uses system resources on WindowsControlling and limiting resourcesBest practices for resource allocationOptimizing container startup and executionWhy startup speed mattersBuilding lean imagesTrim and measure what runs at startupManaging CPU and memory limitsResource usage in WSL2Setting limits on individual containersUsing limits in Docker ComposeScaling Docker environmentsWhy scaling mattersScaling containersWhy Swarm on Windows?Tips for forget-free scalingMonitoring and fine-tuning performanceUsing Docker's built-in toolsAdvanced monitoring and scanningFine-tuning based on real-world usageThe Big Lab: Making the Notes service observableSummary
Chapter 7: Docker GenAI Stack on Windows
Technical requirementsIntroduction to the GenAI stackPlatforms, frameworks, and modelsSecurity considerationsData considerationsGetting into the componentsDeploying AI models with Docker on WindowsChoosing the right base imageWriting the DockerfileBuilding and running on WindowsTuning for Windows performanceLocal monitoringIterating and updatingDeploying a multi-model GenAI stack on WindowsManaging data for AI workflowsIngestion, caching, and vector storageStructuring Compose for a data workflowMonitoring and securing data workflowsMetrics and logsHealth checksScaling considerations for data servicesPVC-like volumes on WindowsBest practices for AI deployments with DockerStart with smarter base imagesMulti-stage builds: Keep what you need, dump what you don'tKeep model weights out of the Docker build (when you can)Avoid mounting from C:\ where possible...seriously!Strip unnecessary packages and dev toolsWatch out for pip cacheBuild arguments for flexibilityKeep it predictable: Define your contracts earlyPrefer composition over complexityBake in default models and fallbacksMake GPU access explicit, not assumedDeploying a secure, multi-service GenAI stack in productionDon't forget the exit conditionsSecure by defaultThe Big Lab: Scaling a GenAI feature in the Notes serviceSummary

Part 3: Docker in Real-World Use Cases
Chapter 8: Implementing Docker for Enterprise Workloads on Windows
Technical requirementsDeploying Docker for enterprise applicationsPreparing enterprise applications for DockerizationManaging base imagesSigning images in CISecuring and optimizing enterprise imagesIntegrating with CI/CD pipelinesNetworking, storage, and Windows container considerationsStorageNetworkingWindows considerationsLogging and monitoringDeploying the Finance DashboardScaling Docker for high availabilityHigh availability with Docker SwarmSpreading workloads with placement constraintsScaling up and downLoad balancing Docker workloadsUnderstanding load balancing in DockerThe role of the routing meshCustomizing service discovery and internal networkingWorking with external load balancersManaging enterprise Docker infrastructureNodes, labels, and tagsKeeping Docker volumes under controlKeeping things predictableManaging resources and observabilityTracking in enterprise-scale Windows setupsSwitching between environments with Docker contextsMaintaining security and hygieneTroubleshooting and support for large workloadsWhere to start when everything's on fireLogs, events, and exit codesWhen resource pressure triggers failuresWhen networking problems cause outagesNetwork outage checklist (Swarm/Compose)When to rebuild versus restartMaking failures easier to supportThe Big Lab: Running the Notes service across machinesSummary
Chapter 9: Docker and Hybrid Cloud Integration
Technical requirementsWhat do we mean by hybrid cloud?How Docker shapes hybrid cloud architectureA practical hybrid lab scenario: One service, two clouds, one deployment workflowManaging multi-cloud deployments with DockerWhy Docker changes the gameHandling config differencesAvoiding common misconfigurations in multi-cloud deploymentsWhere hybrid cloud data workflows break and how Docker helpsBest practices for securing data in hybrid cloudsUse encrypted networksDon't let secrets leak into imagesSecure your volumesWatch your logsReview CI/CD pipelinesKeep identity tightOrchestrating hybrid cloud applications with Docker SwarmDeploying a hybrid stack across AWS and AzureWhy orchestration really matters in hybridBuilding a hybrid swarmDeploying with Compose across cloudsHealth checks and auto-healingSome orchestration tips for hybrid setupsBest practices for Docker in hybrid cloudsUse private registries and mirror imagesEncrypt trafficAutomate the pipelineSecrets stay out of GitMonitor everything, everywherePlan for failureThe Big Lab: Preparing the Notes service for enterprise CI/CD and hybrid infrastructureSummary
Chapter 10: Troubleshooting Docker in Production Environments
Technical requirementsThe production incident: A real production failureThe Docker troubleshooting frameworkConfirm what's actually brokenInterrogate the containerInterrogate the imageVerify the network pathRecover, validate, and prevent regressionsApplying the frameworkConfirm what's actually brokenNext up, interrogate the container!Interrogate the imageVerify the network pathRecover, validate, and prevent regressionsTroubleshooting referencesRecovery, automation, and preventionThe Big Lab: The final incidentIncident 1: Break the API on purposeIncident 2: Introduce a bad environment variableIncident 3: Corrupt notes.jsonIncident 4: Make the frontend unable to reach the APIIncident 5: Drop a container or remove it entirelyClose out: Prove the incident life cycleSummary
Chapter 11: Unlock Your Exclusive Benefits
Unlock this Book’s Free Benefits in 3 Easy Steps
Other Books You May Enjoy
Index

Content preview from Mastering Docker on Windows

Index

AI deployments, with Docker

best practices275 – 289

AI models, with Docker

building and running, on Windows251 – 253

deploying, on Windows247, 248

Dockerfile, writing248 – 251

iterating and updating255, 256

local monitoring254

multi-model GenAI stack, deploying on Windows256 – 259

right base image, selecting248

tuning, for Windows performance253, 254

Advanced Intrusion Detection Environment (AIDE)194

Amazon ECR367

Auditd tools98

Azure Container Registry367

authenticating with323, 324

Azure Kubernetes Service (AKS)367

advanced backup and recovery solutions

for Docker volumes89

auto-healing392

automated backups79

Bacula tools91

backup and recovery strategies79, 80

backup tools

using, with Docker integration91, 92

backups

scheduling, ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Linux Application Development by Example: The Fundamental APIs, 2nd Edition

Publisher Resources

ISBN: 9781836640516

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Mastering Docker on Windows

by Michael D. Smith

Index

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.