|
Size: 398
Comment:
|
Size: 917
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
'''Bridge networks''' are a type of networks used by `dockerd(8)`. |
|
| Line 11: | Line 13: |
| All containers are attached to a network. If one is not specified, the default network is used. This network is special in that there is no name resolution; the only way to communicate between containers is their ephemeral IP addresses. | By default, containers attach to bridge networks. See [[Docker/Networking|here]] to change that. If a bridge network is not specified, the '''default network''' is used. This network is special in that there is no name resolution; the only way to communicate between containers is their ephemeral IP addresses. Furthermore, the default network's use of IPv6 mandatorily matches the `dockerd(8)` configuration. See [[Docker/Configuration#IPv6|here]] to enable it. |
| Line 19: | Line 25: |
| Custom bridge network can be created and destroyed like: | |
| Line 20: | Line 27: |
| {{{ docker network create my-net docker network rm my-net }}} A container can be created on a network by specifying the `--network` option. {{{ }}} |
Docker Bridge Networks
Bridge networks are a type of networks used by dockerd(8).
Default Network
By default, containers attach to bridge networks. See here to change that.
If a bridge network is not specified, the default network is used. This network is special in that there is no name resolution; the only way to communicate between containers is their ephemeral IP addresses.
Furthermore, the default network's use of IPv6 mandatorily matches the dockerd(8) configuration. See here to enable it.
Creating Networks
Custom bridge network can be created and destroyed like:
docker network create my-net docker network rm my-net
A container can be created on a network by specifying the --network option.