Docker networking ? explained

Docker networking allows containers to communicate with each other and with the external world (outside the Docker host). Docker provides several networking options for managing how containers interact with each other and the host system.

Key Docker Networking Concepts

1. Bridge Network:
   • The default network driver when you create a container. Containers in the bridge network can communicate with each other using their IP addresses or container names but are isolated from external networks (unless port mapping is used).
2. Host Network:
   • Containers share the network namespace of the Docker host. This allows containers to use the host’s network interfaces directly without any isolation. It’s useful when performance is critical and container isolation isn’t required for networking.
3. Overlay Network:
   • Used in Docker Swarm mode to enable communication between containers on different Docker hosts. Overlay networks are especially useful for multi-host Docker setups and allow containers running on different physical machines to communicate as if they were on the same network.
4. None Network:
   • No network is attached to the container. The container is completely isolated from networking, and it’s up to you to manually configure networking if needed.
5. Macvlan Network:
   • Containers are assigned their own MAC addresses and appear as physical devices on the network. This can be useful when you need containers to be directly accessible from an external network, such as when running legacy applications.

---

Default Docker Network Behavior

• Bridge: Containers on the same bridge network can communicate using their container names (acting like a DNS system within the container network). External access to the containers requires port mapping.

---

Docker Networking Commands

1. List Networks:

   docker network ls
   

   This lists all the networks available on your Docker host.

2. Create a Custom Network:

   docker network create --driver <network-driver> <network-name>
   

   Example for a bridge network:

   docker network create --driver bridge my-bridge-network
   

3. Inspect a Network:

   docker network inspect <network-name>
   

   Example:

   docker network inspect my-bridge-network
   

4. Connect a Container to a Network:

   docker network connect <network-name> <container-name>
   

5. Disconnect a Container from a Network:

   docker network disconnect <network-name> <container-name>
   

6. Remove a Network:

   docker network rm <network-name>
   

---

Network Drivers in Docker

1. Bridge Driver:
   • Default driver for containers.
   • Creates a private internal network on the host system and assigns a container an IP on that network.
   • Containers on the same bridge network can communicate with each other, but need port mapping to be accessible externally.
2. Host Driver:
   • Containers use the host’s networking directly, without any isolation.
   • Faster but less secure since containers share the host’s network namespace.
3. Overlay Driver:
   • Used for multi-host networks (Docker Swarm mode).
   • Allows containers on different Docker hosts to communicate over a secure network.
   • Docker handles routing and addressing between hosts.
4. None Driver:
   • The container is not connected to any network.
   • You can configure networking manually if required.
5. Macvlan Driver:
   • Allows containers to have their own MAC addresses and appear as if they are physical devices on the network.
   • Useful for scenarios where containers need direct access to an external network.

---

Network Modes for Containers

• Bridge Network (Default):
  • Containers can communicate with each other but are isolated from external networks (unless port mapping is used).
  • Useful for most use cases when containers need to communicate with each other on the same host.
• Host Network:
  • The container shares the host’s network interfaces.
  • Suitable for high-performance applications where container network isolation is not necessary.
  • Example:

    docker run --network host <image-name>
    

• Overlay Network:
  • Used in Docker Swarm to connect containers across different hosts.
  • Example:

    docker network create --driver overlay my-overlay-network
    

---

Connecting Containers on the Same Network

• Using Container Names:
  • Containers on the same network can access each other using their container names as hostnames. Example:
  • If you have two containers web and db running on the same bridge network, the web container can access the db container using db as the hostname:

  docker run -d --name web --network my-bridge-network <image-name>
  docker run -d --name db --network my-bridge-network <image-name>
  

  • Now, the web container can access the db container with db:port (if needed).

---

Docker Networking Use Cases

1. Multi-container Applications:
   • You can use Docker networks to link multiple containers (e.g., a web application container and a database container) so they can communicate without exposing unnecessary ports to the outside world.
2. Isolated Environments:
   • Docker allows you to create isolated networks for different services, providing security and network isolation between services.
3. Service Discovery in Docker Swarm:
   • In Docker Swarm mode, services running on an overlay network can discover each other via DNS, making it easier to scale and manage services across multiple hosts.
4. External Network Access:
   • When you need a container to be accessible from outside the Docker host, you can use the host or bridge network with port forwarding.

---

Example: Setting Up a Simple Network

1. Create a Bridge Network:

   docker network create --driver bridge my-bridge-network
   

2. Run Two Containers on This Network:

   docker run -d --name container1 --network my-bridge-network nginx
   docker run -d --name container2 --network my-bridge-network nginx
   

3. Inspect Network:

   docker network inspect my-bridge-network
   

   This shows the connected containers and their IP addresses within the network.

---

Let me know if you’d like more examples or further clarification on any Docker networking topics!

For consulting email us at [email protected]