Docker networking

Containers run in isolation and do not see other containers unless you attach them to a Docker network. Legacy container linking is deprecated; user-defined bridge networks are the default mental model.

You have two historical options to let containers communicate on one machine:

• Container Linking (aka legacy linking, deprecated) without any networks involved or
• using Container Networks.

Linking containers is simple to setup, but also limited and should only be used during development.

Option 1: Container Linking (Legacy Linking, deprecated)

Let’s assume you have two containers: The first one is running MongoDB, the second is running NodeJS and you want to connect them via Container Linking. First you give the MongoDB container a name:

1
# Run container with name
2
docker run -d --name my-mongodb mongo

Then your second container (in this example node) can be linked to it:

1
# Link node container to my-mongo and choose alias 'mongodb'
2
docker run -d --link my-mongo:mongodb node

The alias mongodb that you chose is now available as a host within the node container:

1
{
2
  "databaseConfig" : {
3
    "host" : "mongodb",
4
    "database" : "myDatabase"
5
  }
6
}

You can repeat this process if you want to join more containers.

Option 2: Creating a container network

Containers have networking enabled by default, and they can make outgoing connections. If two containers are on the same network (and only then), they can talk to each other using container IP addresses or container names. You can group containers into their own isolated network.

1
# list networks and their drivers
2
docker network ls
3

4
# list containers attached to the network, subnet, gateway and others
5
docker network inspect my-network

First you have to create a custom bridge network. After that there are two ways to put a container on a network:

• Assign the network to a container that you start or
• add an already running container to the network.

1
# create bridged network with name 'isolated-network'
2
docker network create --driver bridge isolated-network

Now, start the first container and attach it to the network:

1
# run detached container and assign network
2
docker run -d \
3
     --network isolated-network \
4
     --network-alias mongodb \
5
     mongo
6

7
# --network is same as --net
8
# --network-alias is same as --net-alias

Having network-alias mongodb allows us to connect to this container using mongodb as host name.

Run the second container and attach it to the same network:

1
# run detached container and assign network
2
docker run -d \
3
     --network isolated-network \
4
     --network-alias node-app \
5
     node

Docker network drivers

Linking multiple containers

If you have many containers it can be tedious to create networks and attach them to it via command line every time. Instead you should use Docker Compose.