Book Image

Learning Windows Server Containers

Book Image

Learning Windows Server Containers

Overview of this book

Windows Server Containers are independent, isolated, manageable and portable application environments which are light weight and shippable. Decomposing your application into smaller manageable components or MicroServices helps in building scalable and distributed application environments. Windows Server Containers have a significant impact on application developers, development operations (DevOps) and infrastructure management teams. Applications can be built, shipped and deployed in a fast-paced manner on an easily manageable and updatable environment. Learning Windows Server Containers teaches you to build simple to advanced production grade container based application using Asp.Net Core, Visual Studio, Azure, Docker and PowerShell technologies. The book teaches you to build and deploy simple web applications as Windows and Hyper-V containers on Windows 10 and Windows Server 2016 on Azure. You will learn to build on top of Windows Container Base OS Images, integrate with existing images from Docker Hub, create custom images and publish to Hub. You will also learn to work with storage containers built using Volumes and SQL Server as container, create and configure custom networks, integrate with Redis Cache containers, configure continuous integration and deployment pipelines using VSTS and Git Repository. Further you can also learn to manage resources for a container, setting up monitoring and diagnostics, deploy composite container environments using Docker Compose on Windows and manage container clusters using Docker Swarm. The last chapter of the book focuses on building applications using Microsoft’s new and thinnest server platform – Nano Servers.
Table of Contents (19 chapters)
Credits
Foreword
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Storage volumes


Docker on Windows Server is responsible for managing images and container storage on the container host. Docker manages this using a separate storage driver and using the copy-on-write mechanism. To serve at a faster pace, Docker stores data in a layered manner; a container is made up of multiple layers. A container's view of a single filesystem is a union of filesystems on each read-only layer which make up the container. The container uses its filesystem to store data but in general the filesystem of the container is an illusion created by the Docker daemon. When a new write happens to any file in the container, Docker creates a copy of the read-only file and places a read-write on the top layer, whilst the underlying read-only copy of the file is never deleted. If the container is deleted, all the changes made to the writable layer are gone forever. If a new container is created using the old image, a new read-only copy of the image is created with a writable layer on...