Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Docker on Windows

You're reading from   Docker on Windows From 101 to production with Docker on Windows

Arrow left icon
Product type Paperback
Published in Feb 2019
Publisher Packt
ISBN-13 9781789617375
Length 428 pages
Edition 2nd Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Elton Stoneman Elton Stoneman
Author Profile Icon Elton Stoneman
Elton Stoneman
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Section 1: Understanding Docker and Windows Containers FREE CHAPTER
2. Getting Started with Docker on Windows 3. Packaging and Running Applications as Docker Containers 4. Developing Dockerized .NET Framework and .NET Core Applications 5. Sharing Images with Docker Registries 6. Section 2: Designing and Building Containerized Solutions
7. Adopting Container-First Solution Design 8. Organizing Distributed Solutions with Docker Compose 9. Orchestrating Distributed Solutions with Docker Swarm 10. Section 3: Preparing for Docker in Production
11. Administering and Monitoring Dockerized Solutions 12. Understanding the Security Risks and Benefits of Docker 13. Powering a Continuous Deployment Pipeline with Docker 14. Section 4: Getting Started on Your Container Journey
15. Debugging and Instrumenting Application Containers 16. Containerize What You Know - Guidance for Implementing Docker 17. Other Books You May Enjoy

Understanding registries and repositories

You download an image from a registry using the docker image pull command. When you run the command, the Docker Engine connects to the registry, authenticates – if it needs to – and pulls the image down. The pull process downloads all the image layers and stores them in the local image cache on the machine. Containers can only be run from images which are available in the local image cache, so unless they're built locally, they need to be pulled first.

One of the earliest commands you run when you get started with Docker on Windows will be something simple, like this example from Chapter 2, Packaging and Running Applications as Docker Containers:

> docker container run dockeronwindows/ch02-powershell-env:2e

Name Value
---- -----
ALLUSERSPROFILE C:\ProgramData...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image