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

This article mainly introduces the example analysis of container interconnection of docke custom network, the article is very detailed, has a certain reference value, interested friends must read it!

-link# clears all containers $root@VM-8-11-ubuntu:~# docker stop $(docker ps-aq) & & docker rm $(docker ps-aq) 88f8f241ca30765ed1889bfa$root@VM-8-11-ubuntu:~# docker run-it-- name=mybusy02-d busybox82aff31e56f3913b3fa883a08ec95960eff88fc9977360a67264c0d53180844b$root@VM-8-11-ubuntu:~# docker run-it-- name mybusy--link mybusy02:mybusy-net-d busyboxb77e9762314f868518f799d3c572dec0b2ce13a684de072fb9f9e925135f6459 $root@VM-8-11-ubuntu:~# docker exec-it mybusy ping mybusy-netPING mybusy-net .17.0.2): 56 data bytes64 bytes from 172.17.0.2: seq=0 ttl=64 time=0.131 ms64 bytes from 172.17.0.2: seq=1 ttl=64 time=0.069 ms64 bytes from 172.17.0.2: seq=2 ttl=64 time=0.069 ms$root@VM-8-11-ubuntu:~# docker exec-it mybusy cat / etc/hosts127.0.0.1 localhost::1 localhost ip6-localhost ip6-loopbackfe00::0 ip6-localnetff00::0 ip6-mcastprefixff02::1 ip6-allnodesff02 :: 2 ip6-allrouters172.17.0.2 mybusy-net 09a4b97fc09d mybusy02 # We found that mybusy02172.17.0.3 c73be07d21fb was added to the hosts file

We found that it is connected, but if mybusy02 wants to ping mybusy, we need another-link. So it's troublesome, and officials recommend that we don't use the parameter-- link.

Docker 0 does not support container name access, and then we come to the highlight of the day, customizing the network.

Custom Network # mainly involves the command $root@VM-8-11-ubuntu:~# docker network-- helpUsage: docker network COMMANDManage networksCommands: connect Connect a container to a network create Create a network disconnect Disconnect a container from a network inspect Display detailed information on one or more networks ls List networks prune Remove all unused networks rm Remove one or more networksRun 'docker network COMMAND-- help' for more information on a command.#, which is the default The network mode brudge is the bridge of docker 0$ root@VM-8-11-ubuntu:~# docker network lsNETWORK ID NAME DRIVER SCOPEcf05ea05d3bd bridge bridge local0ab28e475dc6 host host locale4c628cc77db none null local

Let's use create to create our own bridge network. Basics

#-- driver sets network type-- subnet sets subnet / 16 = 255 ip minus 0.0 and 255.255 equals about $65535 root@VM-8-11-ubuntu:~# docker network create-- driver=bridge-- subnet=192.168.0.0/16 my-net1b668a5439b207d2080d95bffe829139cfa2456d691c8019a245e7f9d5a56970root@VM-8-11-ubuntu:~# docker network lsNETWORK ID NAME DRIVER SCOPEcf05ea05d3bd bridge bridge local0ab28e475dc6 host host local1b668a5439b2 my-net bridge locale4c628cc77db none Null local# View Network Information $root@VM-8-11-ubuntu:~# docker network inspect my-net [{"Name": "my-net" Id: "1b668a5439b207d2080d95bffe829139cfa2456d691c8019a245e7f9d5a56970", "Created": "2021-12-01T09:47:21.410882291+08:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": {"Driver": "default", "Options": {} "Config": [{"Subnet": "192.168.0.0plus 16"}]}, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": {"Network": ""} "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {}]

Above, we introduced how to create a network and how to view it. Next, let's take a look at the methods used.

# create mybusy Container Settings my-net Network $root@VM-8-11-ubuntu:~# docker run-it-- name mybusy-- net=my-net-d busybox180fbc8b04627762a896d8a85d8cb67063c01a0f3ad8a11352ab4695b022c272# create mybusy02 Container Settings my-net Network $root@VM-8-11-ubuntu:~# docker run-it-- name mybusy02-- net=my-net-d busybox3c08d592537a9593c960c9664b4724521658f26be7b658a6483e6fbfe30b58a7# connects $root@VM-8-11-ubuntu:~# docker exec-it mybusy ping mybusy02PING mybusy02 (192.168.0) to container mybusy ping mybusy02 .3): 56 data bytes64 bytes from 192.168.0.3: seq=0 ttl=64 time=0.110 ms64 bytes from 192.168.0.3: seq=1 ttl=64 time=0.070 ms

Then we found that the two of them had ping each other, which was perfect. Let's take a look at the network configuration of my-net below.

Root@VM-8-11-ubuntu:~# docker network inspect my-net [{"Name": "my-net", "Id": "1b668a5439b207d2080d95bffe829139cfa2456d691c8019a245e7f9d5a56970", "Created": "2021-12-01T09:47:21.410882291+08:00", "Scope": "local", "Driver": "bridge", "EnableIPv6": false "IPAM": {"Driver": "default", "Options": {}, "Config": [{"Subnet": "192.168.0.0max 16"}]}, "Internal": false, "Attachable": false "Ingress": false, "ConfigFrom": {"Network": "}," ConfigOnly ": false," Containers ": {# then we found that these two containers had been added to the network" 180fbc8b04627762a896d8a85d8cb67063c01a0f3ad8a11352ab4695b022c272 ": {" Name ":" mybusy "," EndpointID ":" 12929182af47e619e3405cab9981ea1671a2bc31f77d3aa589ebcf2c912c12bc " "MacAddress": "02:42:c0:a8:00:02", "IPv4Address": "192.168.0.2 Name 16", "IPv6Address": ""}, "3c08d592537a9593c960c9664b4724521658f26be7b658a6483e6fbfe30b58a7": {"Name": "mybusy02", "EndpointID": "61b08372535d751cee726fc01d4e300390e2a090dba20f1d21ba96385a7a621e" "MacAddress": "02:42:c0:a8:00:03", "IPv4Address": "192.168.0.3 Labels 16", "IPv6Address": ""}}, "Options": {}, "Labels": {}}] question

Can containers in different network configurations be interconnected?

The answer is yes. We can use the docker network connect directive. Here are the steps.

# first check the two mybusy mybusy02 containers that currently exist in the same network $root@VM-8-11-ubuntu:~# docker ps-aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES3c08d592537a busybox "sh" 8 minutes ago Up 8 minutes mybusy02180fbc8b0462 busybox "sh" 8 minutes ago Up 8 minutes mybusy# to create a mybusy03 $root@ in the default network VM-8-11-ubuntu:~# docker run-it-- name mybusy03-d busyboxa95b57c96f400ed44efffcc938bccce15830fa1ab5b55716261e4588c14429cb# View the current container $root@VM-8-11-ubuntu:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESa95b57c96f40 busybox "sh" 21 seconds ago Up 21 seconds mybusy033c08d592537a busybox "sh" 8 minutes ago Up 8 minutes mybusy02180fbc8b0462 busybox "sh" 9 minutes ago Up 9 minutes mybusy# tries to find that ping does not work from mybusy ping mybusy03 because it is not in the same network end $root@VM-8-11-ubuntu:~# docker exec-it mybusy ping mybusy03ping: bad address' mybusy03'# when we look at the docker network connect-- help command to see $root@VM-8-11-ubuntu:~# docker network connect-- helpUsage: docker network connect [OPTIONS] NETWORK CONTAINERConnect a container to a networkOptions: -- alias strings Add network-scoped alias for the container-- driver-opt strings driver options for the network--ip string IPv4 address (e.g. 172.30.100.104)-- ip6 string IPv6 address (e.g.2001:db8::33)-- link list Add link to another container-- link-local-ip strings Add a link-local address for the container# added mybusy03 to the my-net network $root@VM-8-11-ubuntu:~# docker network connect my-net mybusy03# when we found it through ping. Isn't it amazing $root@VM-8-11-ubuntu:~# docker exec-it mybusy ping mybusy03PING mybusy03 (192.168.0.4): 56 data bytes64 bytes from 192.168.0.4: seq=0 ttl=64 time=0.197 ms64 bytes from 192.168.0.4: seq=1 ttl=64 time=0.087 ms

At this point, we looked at the network and found that mybusy03 had been added to the my-net. So you can get through ping.

The above is all the contents of the article "sample Analysis of Container Interconnection of docke Custom Networks". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

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.