Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing DevOps with Ansible 2

You're reading from   Implementing DevOps with Ansible 2 A step-by-step guide to automating all DevOps stages with ease using Ansible

Arrow left icon
Product type Paperback
Published in Jul 2017
Publisher Packt
ISBN-13 9781787120532
Length 266 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Jonathan McAllister Jonathan McAllister
Author Profile Icon Jonathan McAllister
Jonathan McAllister
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. DevOps Fundamentals FREE CHAPTER 2. Configuration Management Essentials 3. Installing, Configuring, and Running Ansible 4. Playbooks and Inventory Files 5. Playbooks – Beyond the Fundamentals 6. Jinja in Ansible 7. Ansible Vault 8. Ansible Modules and Libraries 9. Integrating Ansible with CI and CD Solutions 10. Ansible and Docker 11. Extending Ansible 12. Ansible Galaxy

Managing Docker Images with Ansible

Docker images are slightly different from containers. That is, the image is the stored copy of the container. Docker images are stored in what is commonly referred to as a registry. In the context of Docker, the registry acts similar to a source control solution in many ways. That source control solution is mirrored in many ways to Git. Docker registries parallel Git in many ways; the most obvious is the ability to have a distributed set of registries. Confused yet? Let's take a look at the following diagram:

From the preceding illustration, we can see that the Docker registry is a remote location that stores Docker images. Docker images then reside in a local registry (local to the developer) where they can manipulate and store changes made to the various containers stored within the Docker registry. When a set of changes has been deemed...

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