Book Image

Docker on Windows

By : Elton Stoneman
Book Image

Docker on Windows

By: Elton Stoneman

Overview of this book

Docker is a platform for running server applications in lightweight units called containers. You can run Docker on Windows Server 2016 and Windows 10, and run your existing apps in containers to get significant improvements in efficiency, security, and portability. This book teaches you all you need to know about Docker on Windows, from 101 to deploying highly-available workloads in production. This book takes you on a Docker journey, starting with the key concepts and simple examples of how to run .NET Framework and .NET Core apps in Windows Docker containers. Then it moves on to more complex examples—using Docker to modernize the architecture and development of traditional ASP.NET and SQL Server apps. The examples show you how to break up monoliths into distributed apps and deploy them to a clustered environment in the cloud, using the exact same artifacts you use to run them locally. To help you move confidently to production, it then explains Docker security, and the management and support options. The book finishes with guidance on getting started with Docker in your own projects, together with 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 (20 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Dockerizing what you know


When you move to a new application platform, you have to work with a new set of artifacts and new operational processes. If you currently use the Windows installer for deployment, your artifacts are Wix files and MSIs. Your deployment process is to copy the MSI to the target server, log on, and run the installer.

After the move to Docker, you will have Dockerfiles and images as the deployment artifacts. You push the image to a registry and run a container or update a service to deploy the app. The resources and activities are simpler in Docker, and they'll be consistent between projects, but there's still a learning curve when you start.

Containerizing an app that you know well is a great way to provide a solid basis to that learning experience. When you first run your app in a container, you may see errors or incorrect behavior but that will be in the domain of your own application. When you're tracking down the issue, you'll be dealing with an area you understand...