Hello readers,

This blog will tell you about the docker bridge network. Its use with some basic use cases also how to bridge networks different from the network.

One of the reasons Docker containers and services are so powerful is that you can connect them together, or connect them to non-Docker workloads.

Docker Network

Docker’s networking subsystem is pluggable, using drivers. Several drivers exist by default, and provide core networking functionality:

Type of docker Network :

• bridge: The default network driver. If you don’t specify a driver, this is the type of network you are creating. Bridge networks allow your applications to run in standalone containers that need to communicate.
• host: For standalone containers, remove network isolation between the container and the Docker host, and use the host’s networking directly. The host is available for swarm services on Docker 17.06 and higher.
• overlay: Overlay networks connect multiple Docker daemons together and enable swarm services to communicate with each other. You can also use overlay networks to facilitate communication between a swarm service and a standalone container, or between two standalone containers on different Docker daemons.
• macvlan: Macvlan networks allow you to assign a MAC address to a container, making it appear as a physical device on your network. The Docker daemon routes traffic to containers by their MAC addresses.
• none: For this container, disable all networking. Usually used in conjunction with a custom network driver.

Let create a bridge network with name alpine-net . Start two alpine container and ping between them to check network connectivity.

$ docker network create --driver bridge alpine-net
962f373dd1cc9b9d532287b898e56d51fe1e5cf09fe90208ccbf34e51ea4511c

#devops #docker #docker bridge network #docker network