We have just explored the default bridge network.
Its name is actually Bridge and we have explored that.
Those two containers, BusyBox one and BusyBox two, are currently assigned to this network and that's
why they have addresses from this range.
172 17 zero zero slash 16 Here is IP address of BusyBox one container and here is IP address of BusyBox
two container.
Now let me demonstrate you how we are able to create new custom network with new network range.
For that, we will use command, Docker, network, create.
Let's do that.
Let's clear terminal and here type Docker network create and here will be name of the new network and
let's give it name simply custom like so let's press enter and here you will see ID of the network that
was just created.
Let's now list networks that currently exist in Docker, Docker Network LS and you will see additional
custom network that was just created and its driver is bridge.
Same as for Default bridge network.
And here is ID of this custom network.
Great.
Let's now inspect this custom network using Docker network, inspect command, Docker network, inspect
custom or you are able to use this ID, Let's press enter and here are details about this custom network.
If I'll scroll up, you'll see details about this newly created custom network.
Here is its ID, Here is time when it was created.
Here is Driver Bridge and here are details about this network.
Here is subnet 172 18 zero zero slash 16.
It is also private network, but you see that this prefix differs from the prefix in default bridge
network.
There was prefix 172.17 and this one has prefix 172 18.
That is actually completely different sub network and the containers in this network will be able to
communicate between each other, but they will not be able to communicate with default bridge network.
Great.
Also you'll see here Gateway 172 18 0.1.
This address is assigned to Docker host and now actually Docker host is connected to both bridge networks
to default and to custom.
And of course, any containers that will be assigned to this custom network will have access to internet
and they will be able to download some additional packages if they need to or publish some changes and
so on.
Anyway, they will be able to communicate with internet without any problems.
Great.
That's how we were able to create new custom network and now it's a good time to assign to create containers
in this custom network.
But let's do that after the pause.
By by.