Mastering Docker, Fourth Edition

Russ McKendrick

• Editore: Packt Publishing
• Anno: 2020
• ISBN:
  9781839213519
• Argomento: Computer Science
• Categoria: Systems Architecture

Unlock the full potential of the Docker containerization platform with this practical guide

Key Features

• Explore tools such as Docker Engine, Machine, Compose, and Swarm
• Discover how you can integrate Docker into your everyday workflows
• Get well-versed with Kubernetes options such as Minikube, Kind, and MicroK8s

Book Description

Docker has been a game changer when it comes to how modern applications are deployed and created. It has now grown into a key driver of innovation beyond system administration, with a significant impact on the world of web development. Mastering Docker shows you how you can ensure that you're keeping up with the innovations it's driving and be sure you're using it to its full potential. This fourth edition not only demonstrates how to use Docker more effectively but also helps you rethink and reimagine what you can achieve with it.You'll start by building, managing, and storing images along with exploring best practices for working with Docker confidently. Once you've got to grips with Docker security, the book covers essential concepts for extending and integrating Docker in new and innovative ways. You'll also learn how to take control of your containers efficiently using Docker Compose, Docker Swarm, and Kubernetes.By the end of this Docker book, you'll have a broad yet detailed sense of what's possible with Docker and how seamlessly it fits in with a range of other platforms and tools.

What you will learn

• Get to grips with essential Docker components and concepts
• Discover the best ways to build, store, and distribute container images
• Understand how Docker can fit into your development workflow
• Secure your containers and files with Docker s security features
• Explore first-party and third-party cluster tools and plugins
• Launch and manage your Kubernetes clusters in major public clouds

Who this book is for

If you are a software architect, DevOps engineer, sysadmin, or IT professional looking to leverage Docker's extensive features for innovating any process from system administration to web development, Mastering Docker will show you how you can use it to its full potential. A basic understanding of containerization and prior Docker experience is necessary.

]]>

Section 1: Getting Up and Running with Docker

In this section, you will learn how to install, configure, and use Docker to launch both simple and complex containerized applications on a local machine.

This section comprises the following chapters:

Chapter 1, Docker Overview

Chapter 2, Building Container Images

Chapter 3, Storing and Distributing Images

Chapter 4, Managing Containers

Chapter 5, Launching Multiple Containers Using Docker Compose

Chapter 6, Using Docker Machine,Vagrant, and Multipass

Chapter 1: Docker Overview

Welcome to Mastering Docker, Fourth Edition! This first chapter will cover the Docker basics that you should already have a pretty good handle on. But if you don't already have the required knowledge at this point, this chapter will help you get up to speed, so that subsequent chapters don't feel as heavy.

By the end of the book, you will be a Docker master able to implement Docker in your environments, building and supporting applications on top of them.

In this chapter, we're going to review the following:

• Understanding Docker
• The differences between dedicated hosts, virtual machines, and Docker installers/installation
• The Docker command
• The Docker and container ecosystem

Technical requirements

In this chapter, we are going to discuss how to install Docker locally. To do this, you will need a host running one of the three following operating systems:

• macOS High Sierra and above
• Windows 10 Professional
• Ubuntu 18.04 and above
• Check out the following video to see the Code in Action: https://bit.ly/35fytE3

Understanding Docker

Before we look at installing Docker, let's begin by getting an understanding of the problems that the Docker technology aims to solve.

Developers

The company behind Docker, also called Docker, has always described the program as fixing the 'it works on my machine' problem. This problem is best summed up by an image, based on the Disaster Girl meme, which simply had the tagline 'Worked fine in dev, ops problem now', that started popping up in presentations, forums, and Slack channels a few years ago. While it is funny, it is, unfortunately, an all-too-real problem and one I have personally been on the receiving end of, let's take a look at an example of what is meant by this.

The problem

Even in a world where DevOps best practices are followed, it is still all too easy for a developer's working environment to not match the final production environment.

For example, a developer using the macOS version of, say, PHP will probably not be running the same version as the Linux server that hosts the production code. Even if the versions match, you then have to deal with differences in the configuration and overall environment on which the version of PHP is running, such as differences in the way file permissions are handled between different operating system versions, to name just one potential problem.

All of this comes to a head when it is time for a developer to deploy their code to the host, and it doesn't work. So, should the production environment be configured to match the developer's machine, or should developers only do their work in environments that match those used in production?

In an ideal world, everything should be consistent, from the developer's laptop all the way through to your production servers; however, this utopia has traditionally been challenging to achieve. Everyone has their way of working and their own personal preferences—enforcing consistency across multiple platforms is difficult enough when a single engineer is working on the systems, let alone a team of engineers working with a team of potentially hundreds of developers.

The Docker solution

Using Docker for Mac or Docker for Windows, a developer can quickly wrap their code in a container that they have either defined themselves or created as a Dockerfile while working alongside a sysadmin or operations team. We will be covering this in Chapter 2, Building Container Images, as well as Docker Compose files, which we will go into more detail about in Chapter 5, Docker Compose.

Programmers can continue to use their chosen integrated development environment (IDE) and maintain their workflows when working with the code. As we will see in the upcoming sections of this chapter, installing and using Docker is not difficult; considering how much of a chore it was to maintain consistent environments in the past, even with automation, Docker feels a little too easy – almost like cheating.

Operators

I have been working in operations for more years than I would like to admit, and the following problem has cropped regularly.

The problem

Let's say you are looking after five servers: three load-balanced web servers and two database servers that are in a master or slave configuration dedicated to running Application 1. You are using a tool, such as Puppet or Chef, to automatically manage the software stack and configuration across your five servers.

Everything is going great until you are told that we need to deploy Application 2 on the same servers that are running Application 1. On the face of it, this is not a problem – you can tweak your Puppet or Chef configuration to add new users, add virtual hosts, pull the latest code down, and so on. However, you notice that Application 2 requires a newer version of the software than the one you are running for Application 1.

To make matters worse, you already know that Application 1 flat out refuses to work with the new software stack and that Application 2 is not backward compatible.

Traditionally, this leaves you with a ...

Indice dei contenuti

• Mastering Docker, Fourth Edition
• Why subscribe?
• Preface
• Section 1: Getting Up and Running with Docker
• Chapter 1: Docker Overview
• Chapter 2: Building Container Images
• Chapter 3: Storing and Distributing Images
• Chapter 4: Managing Containers
• Chapter 5: Docker Compose
• Chapter 6: Docker Machine, Vagrant, and Multipass
• Section 2: Clusters and Clouds
• Chapter 7: Moving from Linux to Windows Containers
• Chapter 8: Clustering with Docker Swarm
• Chapter 9: Portainer – A GUI for Docker
• Chapter 10: Running Docker in Public Clouds
• Chapter 11: Docker and Kubernetes
• Chapter 12: Discovering other Kubernetes options
• Chapter 13: Running Kubernetes in Public Clouds
• Section 3: Best Practices
• Chapter 14: Docker Security
• Chapter 15: Docker Workflows
• Chapter 16: Next Steps with Docker
• Assessments
• Other Books You May Enjoy