Docker network自定義網絡方式
Docker network自定義網絡
現在官方已經廢棄了 run --link 的使用(可通過容器名來 Ping 通),所以我們可以采用自定義網絡的做法來聯通容器
第一步
組建子網,我取名為 nettest
docker network create --driver bridge --subnet 192.168.0.0/16 --gateway 192.168.0.1 nettest
注意我這里是使用IP地址前16位作為CIDR前綴,不要和集群內的其他子網沖突

可用 docker network inspect nettest 指令查看子網信息
[
{
"Name": "nettest",
"Id": "241ec33539eae571bd0ce269f9b6ec8525dfbbe5e96d1c7e00539fa10a0adc10",
"Created": "2022-03-31T13:07:44.672058045+08:00",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": {},
"Config": [
{
"Subnet": "192.168.0.0/16",
"Gateway": "192.168.0.1"
}
]
},
"Internal": false,
"Attachable": false,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {},
"Options": {},
"Labels": {}
}
]第二步
向nettest子網添加容器,這里我將兩個我自己定義的centos容器加入了該子網
docker run -d -P --name centos-net-01 --net nettest mycentos docker run -d -P --name centos-net-02 --net nettest mycentos
如果不指定net,則會自動加入bridge網絡(對應于docker0網橋)

此時再次查看子網信息
[
{
"Name": "nettest",
"Id": "241ec33539eae571bd0ce269f9b6ec8525dfbbe5e96d1c7e00539fa10a0adc10",
"Created": "2022-03-31T13:07:44.672058045+08:00",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": {},
"Config": [
{
"Subnet": "192.168.0.0/16",
"Gateway": "192.168.0.1"
}
]
},
"Internal": false,
"Attachable": false,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {
"126e1b28a5958ee159fa16073501cbc61508ce803ccaab1682489fb859fe6ae3": {
"Name": "centos-net-02",
"EndpointID": "14ae44c2a7f9b7572b814e86c06fef3597d5eb2308ea588c91cabe38d22ec426",
"MacAddress": "02:42:c0:a8:00:03",
"IPv4Address": "192.168.0.3/16",
"IPv6Address": ""
},
"903a5af6d1050998523a23b10f0dcee86f7d8a35cca8544ea5499b5cd6d22c9f": {
"Name": "centos-net-01",
"EndpointID": "7c1ff29b1fad9df3943d4d3eda6520cce66ebcbe61a8c5127b3161ddb7f6649a",
"MacAddress": "02:42:c0:a8:00:02",
"IPv4Address": "192.168.0.2/16",
"IPv6Address": ""
}
},
"Options": {},
"Labels": {}
}
]可以發(fā)現 "Containers" 下多了兩個容器對象
而網關為宿主機

第三步
測試子網內的容器是否能聯通

可以發(fā)現通過容器名和其對應的內網IP都能Ping通
而這種自定義網絡我在容器的/etc/hosts中并沒有看到其他容器的域名IP映射

如果后續(xù)還需要向該子網添加容器,可以使用以下指令
docker network connect multi-host-network container1
[root@Hadoop100 docker-test-volume]# docker network connect nettest centos-net-03
[root@Hadoop100 docker-test-volume]# docker network inspect nettest
[
{
"Name": "nettest",
"Id": "241ec33539eae571bd0ce269f9b6ec8525dfbbe5e96d1c7e00539fa10a0adc10",
"Created": "2022-03-31T13:07:44.672058045+08:00",
"Scope": "local",
"Driver": "bridge",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": {},
"Config": [
{
"Subnet": "192.168.0.0/16",
"Gateway": "192.168.0.1"
}
]
},
"Internal": false,
"Attachable": false,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {
"126e1b28a5958ee159fa16073501cbc61508ce803ccaab1682489fb859fe6ae3": {
"Name": "centos-net-02",
"EndpointID": "14ae44c2a7f9b7572b814e86c06fef3597d5eb2308ea588c91cabe38d22ec426",
"MacAddress": "02:42:c0:a8:00:03",
"IPv4Address": "192.168.0.3/16",
"IPv6Address": ""
},
"163f33f66ba95bc9ee7dece20f87fe7c18ec290cd2618145bba1a07d7ebf2b6e": {
"Name": "centos-net-03",
"EndpointID": "6854d517cae02fa4b41fdd4c6406afd61c6529a573257829bc78003dca01b079",
"MacAddress": "02:42:c0:a8:00:04",
"IPv4Address": "192.168.0.4/16",
"IPv6Address": ""
},
"903a5af6d1050998523a23b10f0dcee86f7d8a35cca8544ea5499b5cd6d22c9f": {
"Name": "centos-net-01",
"EndpointID": "7c1ff29b1fad9df3943d4d3eda6520cce66ebcbe61a8c5127b3161ddb7f6649a",
"MacAddress": "02:42:c0:a8:00:02",
"IPv4Address": "192.168.0.2/16",
"IPv6Address": ""
}
},
"Options": {},
"Labels": {}
}
]我之前使用run --link來聯通容器時,發(fā)現其中被link的源容器被我stop后兩個容器都從docker進程中消失了,而這種自定義網絡則不會出現這種奇怪的現象
最后需要強調一點,千萬不要試圖去使用 docker network rm -f $(docker network ls -q) 這種指令,這可能會把docker默認創(chuàng)建的網絡也給刪去!
總結
以上為個人經驗,希望能給大家一個參考,也希望大家多多支持腳本之家。
相關文章
Docker搭建代碼檢測平臺SonarQube并檢測maven項目的流程
這篇文章主要介紹了Docker搭建代碼檢測平臺SonarQube并檢測maven項目,本文給大家介紹的非常詳細,對大家的學習或工作具有一定的參考借鑒價值,需要的朋友可以參考下2020-05-05
使用docker -v 和 Publish over SSH插件實現war包自動部署到docker的操作步驟
這篇文章主要介紹了利用docker -v 和 Publish over SSH插件實現war包自動部署到docker的操作步驟,非常不錯,具有參考借鑒價值,需要的朋友可以參考下2018-01-01

