Search icon CANCEL
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
Hands-On Linux Administration on Azure

You're reading from   Hands-On Linux Administration on Azure Develop, maintain, and automate applications on the Azure cloud platform

Arrow left icon
Product type Paperback
Published in Feb 2020
Publisher Packt
ISBN-13 9781839215520
Length 508 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Rithin Skaria Rithin Skaria
Author Profile Icon Rithin Skaria
Rithin Skaria
Frederik Vos Frederik Vos
Author Profile Icon Frederik Vos
Frederik Vos
Kamesh Ganesan Kamesh Ganesan
Author Profile Icon Kamesh Ganesan
Kamesh Ganesan
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Chapter 1: Exploring the Microsoft Azure Cloud 2. Chapter 2: Getting Started with the Azure Cloud FREE CHAPTER 3. Chapter 3: Basic Linux Administration 4. Chapter 4: Managing Azure 5. Chapter 5: Advanced Linux Administration 6. Chapter 6: Managing Linux Security and Identities 7. Chapter 7: Deploying Your Virtual Machines 8. Chapter 8: Exploring Continuous Configuration Automation 9. Chapter 9: Container Virtualization in Azure 10. Chapter 10: Working with Azure Kubernetes Service 11. Chapter 11: Troubleshooting and Monitoring Your Workloads 12. Chapter 12: Appendix 13. Index

Docker

In March 2010, Solomon Hykes started the development of Docker. It started in France as an internal dotCloud. Thanks to the public release at a big Python conference in 2013 and the interest of Red Hat, Docker really took off. In the last quarter of that same year, the name of the company was changed to Docker Inc.

Docker was originally built on top of LXC but after a while, LXC was replaced by their own libcontainer library.

The architecture of Docker is quite complex: it consists of a client, Docker, and a daemon, dockerd. Another daemon, containerd, is an abstraction layer for the OS and the type of container technology that is being used. You can interact with containerd using the docker- containerd-ctr utility. The containerd daemon is responsible for the following:

  • The registry (where you can store images)
  • The image (building, metadata, and so on)
  • Networking
  • Volumes (to store persistent data)
  • Signing (trust on content)

containerd communicates...

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