Book Image

Learn Docker - Fundamentals of Docker 19.x - Second Edition

By : Dr. Gabriel N. Schenker
Book Image

Learn Docker - Fundamentals of Docker 19.x - Second Edition

By: Dr. Gabriel N. Schenker

Overview of this book

Containers enable you to package an application with all the components it needs, such as libraries and other dependencies, and ship it as one package. Docker containers have revolutionized the software supply chain in both small and large enterprises. Starting with an introduction to Docker fundamentals and setting up an environment to work with it, you’ll delve into concepts such as Docker containers, Docker images, and Docker Compose. As you progress, the book will help you explore deployment, orchestration, networking, and security. Finally, you’ll get to grips with Docker functionalities on public clouds such as Amazon Web Services (AWS), Azure, and Google Cloud Platform (GCP), and learn about Docker Enterprise Edition features. Additionally, you’ll also discover the benefits of increased security with the use of containers. By the end of this Docker book, you’ll be able to build, ship, and run a containerized, highly distributed application on Docker Swarm or Kubernetes, running on-premises or in the cloud.
Table of Contents (25 chapters)
1
Section 1: Motivation and Getting Started
4
Section 2: Containerization, from Beginner to Black Belt
11
Section 3: Orchestration Fundamentals and Docker Swarm
18
Section 4: Docker, Kubernetes, and the Cloud

Running in an existing network namespace

Normally, Docker creates a new network namespace for each container we run. The network namespace of the container corresponds to the sandbox of the container network model we described earlier on. As we attach the container to a network, we define an endpoint that connects the container network namespace with the actual network. This way, we have one container per network namespace.

Docker provides an additional way for us to define the network namespace that a container runs in. When creating a new container, we can specify that it should be attached to (or maybe we should say included) in the network namespace of an existing container. With this technique, we can run multiple containers in a single network namespace:

Multiple containers running in a single network namespace

In the preceding diagram, we can see that...