Understanding Docker Networking — Part II

Table of Contents

1. Overview
2. Standalone Docker Networking
   2.1 Default Bridge Network
3. User-defined Bridge Networks
   3.1 The Host Network
   3.2 Macvlan Network
   3.3 None
4. Distributed Networking
   4.1 Overlay Networks
   4.2 Ingress
5. Docker Network Plugins‍

1. Overview

Docker can be used in various use cases: the standalone mode, using Docker Compose, in a single host, or by deploying containers and connecting Docker engines across multiple hosts. The user can use Docker containers with the default network, the host network, or other types of more advanced networks like overlays. This depends on the use case and/or the adopted technologies.

In this tutorial, we are going to understand the different types of container networking. We are also going to study containers networking. We will see different types of networking, and finally, we will understand how to extend Docker networking using plugins. This article is the second part of a series. For part I, check out this article.

2. Standalone Docker Networking

2.1 Default Bridge Network

After a fresh Docker installation, you can find a default bridge network up and running.

We can see it by typing

docker network ls

If you use ifconfig command, you will also notice that this network interface is called “docker0”:

All Docker installations have this network. If you run a container, say, Nginx, it will be attached by default to the bridge network …

…

To finish reading this article, check out the full post on the MetricFire website.