Shulou(Shulou.com)06/01 Report--

This article will explain in detail the example analysis of Docker network commands for you. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

Docker network create

Docker network connect

Docker network ls

Docker network rm

Docker network disconnect

Docker network inspect

Create a network

Zane@zane-V:~$ docker network create simple-networkzane@zane-V:~$ docker network inspect simple-network {"Name": "simple-network", "Id": "8bf58f43c56622d1100f7da9ef6506e45a4aa68556b586311f3756130c311d75", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": {"Driver": "default", "Options": {} "Config": [{"Subnet": "172.20.0.0 Containers 16", "Gateway": "172.20.0.1 Labels 16"}]}, "Internal": false, "Containers": {}, "Options": {}, "Labels": {}}

Enter a key value store. The engine supports Consul,Etcd,ZooKeeper.

Deamon engine correctly configured on each host in the cluster

Docker options that support overlay networks:

-- cluster-store-opt

Use the-- subnet option to specify subnetworks directly, only one subnetwork can be specified in a bridge network, and multiple subnetworks are supported in an overlay network.

In addition to-- subnet, you can also specify the:-- gateway,--ip-range,--aux-address option.

$docker network create-d overlay\-- subnet=192.168.0.0/16\-- subnet=192.170.0.0/16\-- gateway=192.168.0.100\-- gateway=192.170.0.100\-- ip-range=192.168.1.0/24\-- aux-address= "my-switch=192.168.1.6"\-aux-address= "my-nas=192.170.1.6"\

Docker also supports many options on how to create your own customized network.

You can specify the port number of the network:

$docker run-d-P-name redis-network my-network redis $docker psCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESbafb0c808c53 redis "/ entrypoint.sh redis" 4 seconds ago Up 3 seconds 172.23.0.1 docker run 32770-> 6379/tcp redis

Connect the container

You can connect existing containers to one or more networks. A container can be connected to multiple different network-driven networks.

Once the connection is established, the container can communicate with other containers, via IP or container name.

Basic container network instance:

1. Create two containers, container1 and container2

$docker run-itd-- name=container1 busybox $docker run-itd-- name=container2 busyboxzane@zane-V:~$ docker network create-d bridge-- subnet 172.25.0.0amp 16 isolated_nw

3. Connect container2 to this network and verify:

Zane@zane-V:~$ docker network connect isolated_nw container2 zane@zane-V:~$ docker network inspect isolated_nw {"Name": "isolated_nw", "Id": "a8208641505d2d8fc37bf7cbd1027c01f0def461815786e076ef4ae65b7b2f9b", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": {"Driver": "default", "Options": {} "Config": [{"Subnet": "172.25.0.0Name 16"}}, "Internal": false, "Containers": {"e9bce535ae32945f5e43340facdb6c16c93d92119e85b61c6cb7a5379a0caf63": {"Name": "container2", "EndpointID": "ef7244d32484407c3ec4aa30b7bdb0a6cbe3dbbfedc03e5c856ad20a08af172f", "MacAddress": "02:42:ac:19:00:02", "IPv4Address": "172.25.0.2 IPv4Address" "IPv6Address": ""}}, "Options": {}, "Labels": {}}

Notice container2, which is automatically assigned to the IP address. At this point, container1 is still connected to the default bridge network.

4. Start the third container, but this is to specify its IP address using the-- ip option

Zane@zane-V:~$ docker run-network=isolated_nw-ip=172.25.3.3-itd-name=container3 busybox

5. Check which network container3 is using:

"Networks": {"isolated_nw": {"IPAMConfig": {"IPv4Address": "172.25.3.3"}, "Links": null, "Aliases": ["adf68dd9e09c"], "NetworkID": "a8208641505d2d8fc37bf7cbd1027c01f0def461815786e076ef4ae65b7b2f9b", "EndpointID": "71d5d272d056b6111a83f0843a10d1944f1648f34d5099258d5865d053a939b0", "Gateway": "172.25.0.1" "IPAddress": "172.25.3.3", "IPPrefixLen": 16, "IPv6Gateway": "," GlobalIPv6Address ":"," GlobalIPv6PrefixLen ": 0," MacAddress ":" 02:42:ac:19:03:03 "}

6. Check which network container2 is using:

"Networks": {"isolated_nw": {"Aliases": ["e9bce535ae32"], "EndpointID": "ef7244d32484407c3ec4aa30b7bdb0a6cbe3dbbfedc03e5c856ad20a08af172f", "Gateway": "172.25.0.1", "GlobalIPv6Address": "", "GlobalIPv6PrefixLen": 0, "IPAMConfig": {}, "IPAddress": "172.25.0.2", "IPPrefixLen": 16 "IPv6Gateway": "," Links ": null," MacAddress ":" 02:42:ac:19:00:02 "," NetworkID ":" a8208641505d2d8fc37bf7cbd1027c01f0def461815786e076ef4ae65b7b2f9b "}}

Note: container2 is between the two networks, it joins the default bridge network, and when you create it, then connect it to isolation_nw.

A container can be connected to multiple networks

7. Use the docker attach command to connect to a running container, and then view

Zane@zane-V:~$ docker attach container2/ # ifconfig-aeth2 Link encap:Ethernet HWaddr 02:42:AC:19:00:02 inet addr:172.25.0.2 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: fe80::42:acff:fe19:2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:86 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns : 0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11780 (11.5 KiB) TX bytes:648 (648.0 B) eth3 Link encap:Ethernet HWaddr 02:42:AC:11:00:03 inet addr:172.17.0.3 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: fe80::42:acff:fe11:3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:23 errors:0 dropped:0 Overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3809 (3.7 KiB) TX bytes:648 (648.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: 1Accord 128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets : 0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0B) TX bytes:0 (0.0B)

8. You can connect to each other by container name

/ # ping-w 4 container3PING container3 (172.25.3.3): 56 data bytes64 bytes from 172.25.3.3: seq=0 ttl=64 time=0.077 ms64 bytes from 172.25.3.3: seq=1 ttl=64 time=0.049 ms64 bytes from 172.25.3.3: seq=2 ttl=64 time=0.047 ms64 bytes from 172.25.3.3: seq=3 ttl=64 time=0.054 ms

Although container1 and container2 are both in the bridge network, they do not support container name communication.

Zane@zane-V:~$ docker attach container2/ # ping container3PING container3 (172.25.3.3): 56 data bytes64 bytes from 172.25.3.3: seq=0 ttl=64 time=0.042 ms64 bytes from 172.25.3.3: seq=1 ttl=64 time=0.050 ms64 bytes from 172.25.3.3: seq=2 ttl=64 time=0.063 ms--- container3 ping statistics-3 packets transmitted, 3 packets received 0 packet lossround-trip min/avg/max = 0.042 data bytes64 bytes from 0.051 ms / # ping-w 4 container1ping: bad address' container1' / # ping-w 4 172.17.0.2PING 172.17.0.2 (172.17.0.2): 56 data bytes64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.104 ms64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.052 ms64 bytes from 172.17.0.2: seq=2 ttl=64 time=0.127 Ms64 bytes from 172.17.0.2: seq=3 ttl=64 time=0.057 ms-172.17.0.2 ping statistics-4 packets transmitted 4 packets received, 0% packet lossround-trip min/avg/max = 0.052 ms 0.085 ms

Note that when exiting attach, use ctr-p + ctr-q.

If you use ctr-d, you will stop container.

Zane@zane-V:~$ docker attach container3/ # ping-w 4 172.17.0.2PING 172.17.0.2 (172.17.0.2): 56 data bytes-172.17.0.2 ping statistics-4 packets transmitted, 0 packets received, 100% packet loss

In the above experiment, we know that the user-defined network can resolve container names with each other, that is, they can walk with each other with container names.

Define a network alias-link=CONTAINER-NAME:ALIAS

1. Disconnect container2 from isolated_nw, and then

Zane@zane-V:~$ docker network disconnect isolated_nw container2zane@zane-V:~$ docker network rm simple-network

Create a network docker network create simple-network

Overlay network conditions enter a key storage

Docker option that supports overlay network-- cluser-store

Specify subnetwork, gateway, address range

Add containers to the network docker network connect isolated_nw container2

Connect a running container docker attach

Attach exits ctr p + ctr Q

Default bridge network does not support container name communication, other network support; use link to support container name communication of default network

Disconnect

Docker network disconnect isolated_nw container2

Delete a network

Docker network rm simple-network

Detection network

Docker network inspect isolated_nw

This is the end of the article on "sample Analysis of Docker Network commands". I hope the above content can be helpful to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.