Docker Docker Networking Docker Networking Drivers bridge host none overlay macvlan ipvlan

1. Core Command / Concept

Docker Networking Drivers allow you to create isolated networks for your containers. docker network create

2. Step-by-Step

1. Check the current Docker network drivers available: docker network ls
2. Create a new bridge network: docker network create --driver bridge my-bridge-network
3. Verify the network was created: docker network ls
4. Create a new container connected to the bridge network: docker run -it --net my-bridge-network --name my-container ubuntu
5. Check the container's network settings: docker inspect my-container
6. ⚠️ Delete the container: docker rm -f my-container
7. ⚠️ Delete the network: docker network rm my-bridge-network

3. Real Commands with Examples

Example 1: Host Networking

Purpose: Use the host network for a container.
Command: docker run -it --net host --name my-container ubuntu Flags: --net host uses the host network, --name sets the container name.

Example 2: Overlay Networking

Purpose: Create an overlay network for multiple containers.
Command: docker network create --driver overlay my-overlay-network Flags: --driver overlay uses the overlay driver, my-overlay-network sets the network name.

Example 3: Macvlan Networking

Purpose: Create a macvlan network for multiple containers.
Command: docker network create --driver macvlan --subnet 192.168.1.0/24 --gateway 192.168.1.1 my-macvlan-network Flags: --driver macvlan uses the macvlan driver, --subnet sets the subnet, --gateway sets the gateway.

4. Common Errors

Error 1: Network not found

Error message: Error response from daemon: No such network: my-network Why it happens: The network was not created or was deleted.
Fix: docker network create my-network

Error 2: Container not connected to network

Error message: Error response from daemon: Container is not connected to any network Why it happens: The container was not connected to a network.
Fix: docker run -it --net my-network --name my-container ubuntu

Error 3: Network driver not supported

Error message: Error response from daemon: driver not supported: overlay Why it happens: The network driver is not supported on this system.
Fix: Use a supported driver, such as bridge or host.

5. Quick Checks

Scenario 1: Check if a container is connected to a network

Situation: You want to check if a container is connected to a network.
Command: docker inspect my-container Correct response: The container's network settings are listed.

Scenario 2: Check if a network exists

Situation: You want to check if a network exists.
Command: docker network ls Correct response: The network is listed.

Scenario 3: Check the network settings of a container

Situation: You want to check the network settings of a container.
Command: docker inspect my-container Correct response: The container's network settings are listed.

6. Last-Minute Reference

• Docker network drivers: bridge, host, none, overlay, macvlan, ipvlan
• Default network driver: bridge
• ⚠️ Docker network drivers are not supported on all platforms
• Docker network drivers can be used with Docker Compose
• Docker network drivers can be used with Docker Swarm
• Docker network drivers can be used with Kubernetes
• Docker network drivers can be used with other container orchestration tools
• Docker network drivers can be used with Docker Machine
• Docker network drivers can be used with Docker Cloud
• Docker network drivers can be used with Docker Enterprise
• Docker network drivers can be used with Docker Desktop