Basic Docker net­work­ing on a single host

Learn how to use basic and advanced net­work­ing tools to manage Docker con­tain­ers. The net­work­ing feature allows users to define their own networks and connect con­tain­ers to them.

You can create a network on a single host, or on a network that spans multiple hosts using the Docker network feature. This article will cover net­work­ing Docker con­tain­ers on a single host. For in­for­ma­tion and in­struc­tions on net­work­ing Docker con­tain­ers across multiple hosts, see our article on the subject.

• IONOS Linux Cloud Server
• Docker installed and running on your system.

The Docker daemon runs as root, which means that users will need to use sudo to run Docker commands.

To avoid having to use sudo for every Docker command, simply add your user(s) to the docker group with the command:

For example, by adding the user jdoe to the Docker group, this user will no longer have to use sudo for every Docker command. To add the user to the group, use the command:

Each Docker in­stal­la­tion au­to­mat­i­cal­ly builds three default networks. You can list these networks with the command:

The bridge network is the default network. Unless otherwise specified, bridge is the network where Docker will launch any new container.

Docker natively supports two types of networks: bridge and overlay.

• A bridge network is limited to a single host (server).
• An overlay network can span multiple hosts (servers).

Because overlay networks are more com­pli­cat­ed, we will cover them in another article.

In­spect­ing a Docker network will return in­for­ma­tion about that network, including which con­tain­ers are attached to the network, and their IP addresses. This is a valuable testing tool, as well as an easy way to find your con­tain­er's IP address.

You can inspect a network with the command:

For example, to inspect the bridge network, the command is:

As you can see in the above screen­shot, only one container is running on this bridge network. The con­tain­er's name is test_centos_container and the IP address assigned to it is 172.17.0.3.

To create your own network, the command is:

The -d flag lets you specify the driver for the network. For a bridge network, use the bridge driver.

For example, to create a bridge network named new_test_network, use the command:

You can use sudo docker network ls to list the networks on your host and verify that your network has been created.

If you do not specify a network when you start up a container, it will au­to­mat­i­cal­ly be added to the default bridge network.

To start up a container and add it to a specific network, use the command:

For example, to start a container named test_python_container from the python image and add it to a network named new_test_network, the command would be:

Use CTRL-pCTRL-q to detach from the container.

You can use sudo docker network inspect [network name] to check the network and verify that the container is attached.

You can add a running container to a network with the command:

For example, to add a running container named test_centos_container to a network named another_test_network, the command would be:

You can use sudo docker network inspect [network name] to check the network and verify that the container is attached.

To dis­con­nect a container from a network, use the command:

For example to dis­con­nect a container named test_centos_container from the new_test_network network, the command would be:

You can use the command sudo docker network inspect [network name] to inspect the network and verify that the container has been dis­con­nect­ed.

After all of the con­tain­ers that have been added to a network have been stopped or dis­con­nect­ed, you can delete the network with the command:

For example, to remove the network new_test_network, the command would be:

You can verify that the network was removed with the sudo docker network ls command.

For this example we will create a custom bridge network, start up two con­tain­ers on that network, attach to the ping_sender container, and ping the other container ping_receiver from there.

If you prefer to use Ubuntu, simply sub­sti­tute an Ubuntu image instead.

First, create a bridge network named ping_test_network with the command:

Next, start a container named ping_receiver and attach it to the ping_test_network bridge network with the command:

Use CTRL-p CTRL-q to detach from the ping_receiver container.

Inspect the ping_test_network to get the IP address of the ping_receiver container with the command:

In this case, the IP address is 172.19.0.2.

Start a container named ping_sender and attach it to the ping_test_network bridge with the command:

Once you are attached to the container and have a command prompt, ping the other container with the command:

Exit ping with CTRL-c, then use CTRL-pCTRL-q to exit the container.