Docker?容器跨主機(jī)通信?overlay的詳細(xì)步驟
更新時(shí)間：2024年10月14日 11:27:23 作者：蝦丸而已
Overlay網(wǎng)絡(luò)通過(guò)VXLAN技術(shù)創(chuàng)建虛擬網(wǎng)絡(luò),實(shí)現(xiàn)不同主機(jī)上容器的邏輯連接,支持跨主機(jī)通信,具有擴(kuò)展性、隔離性和靈活性,適用于大規(guī)模容器化部署
Docker 容器跨主機(jī)通信 overlay
一.Overlay網(wǎng)絡(luò)概述
? Overlay網(wǎng)絡(luò)是指在不改變現(xiàn)有網(wǎng)絡(luò)基礎(chǔ)設(shè)施的前提下，通過(guò)某種約定通信協(xié)議，把二層報(bào)文封裝在IP報(bào)文之上的新的數(shù)據(jù)格式。Overlay網(wǎng)絡(luò)采用VXLAN（Virtual Extensible LAN）技術(shù)創(chuàng)建一個(gè)虛擬網(wǎng)絡(luò)，將不同主機(jī)上的容器連接到同一個(gè)邏輯網(wǎng)絡(luò)中。這樣，容器就可以像在同一臺(tái)主機(jī)上一樣進(jìn)行通信，而無(wú)需關(guān)心底層的網(wǎng)絡(luò)細(xì)節(jié)。
二.Overlay網(wǎng)絡(luò)的優(yōu)勢(shì)
? 跨主機(jī)通信：Overlay網(wǎng)絡(luò)允許在不同主機(jī)上的容器之間進(jìn)行通信，打破了主機(jī)之間的隔離。
擴(kuò)展性：Overlay網(wǎng)絡(luò)可以支持大量的容器和主機(jī)，滿足大規(guī)模容器化部署的需求。
隔離性：通過(guò)Overlay網(wǎng)絡(luò)，可以為不同的容器提供獨(dú)立的網(wǎng)絡(luò)環(huán)境，避免網(wǎng)絡(luò)沖突和干擾。
靈活性：Overlay網(wǎng)絡(luò)支持動(dòng)態(tài)添加和刪除容器，無(wú)需重新配置網(wǎng)絡(luò)。
三、實(shí)現(xiàn)Overlay網(wǎng)絡(luò)的步驟
1.準(zhǔn)備環(huán)境
docker01 192.168.73.128 ens33 centos7 docker02 192.168.73.129 ens33 centos7
2.初始化一個(gè)swarm集群
# 初始化swarm集群
[root@docker01 ~]# docker swarm init --advertise-addr 192.168.73.128
Swarm initialized: current node (9fn9iyxhkxvjey06lwhgv7zhb) is now a manager.
To add a worker to this swarm, run the following command:
docker swarm join --token SWMTKN-1-1rqzq4jhf4wm77e8yn6s347sd189u84mr0u042kwxxv05n8bbx-1rv4ae95p4e4y6aztlhkvqtfx 192.168.73.128:2377
To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.
# 查看集群
[root@docker01 ~]# docker node ls
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS ENGINE VERSION
9fn9iyxhkxvjey06lwhgv7zhb * docker01 Ready Active Leader 26.1.4
# 查看網(wǎng)絡(luò)
[root@docker01 ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
6ad75bb1b055 bridge bridge local
f12f6a0f8bbf docker_gwbridge bridge local
b1c70e3e1ded host host local
116fnum2qea1 ingress overlay swarm
e9eddadcf473 none null local3.創(chuàng)建 overlay network
# 創(chuàng)建ovelay，自定義子網(wǎng)和網(wǎng)關(guān)，不輸入系統(tǒng)會(huì)自動(dòng)生成
[root@docker01 ~]# docker network create -d overlay --subnet=192.168.100.0/24 --gateway=192.168.100.1 --attachable my-overlay
ue8rewtwd72difwr86gi5wwsl
# -–attachable：允許集群服務(wù)間的容器交互連接或者獨(dú)立的容器之間能夠連接。swarm在設(shè)計(jì)之初是為了service(一組container)而服務(wù)的，因此通過(guò)swarm創(chuàng)建的overlay網(wǎng)絡(luò)在一開(kāi)始并不支持單獨(dú)的container加入其中。但是在docker1.13, 我們可以通過(guò)“–attach” 參數(shù)聲明當(dāng)前創(chuàng)建的overlay網(wǎng)絡(luò)可以被container直接加入。
[root@docker01 ~]# docker network inspect my-overlay
[
{
"Name": "my-overlay",
"Id": "ue8rewtwd72difwr86gi5wwsl",
"Created": "2024-10-12T06:04:04.784641012Z",
"Scope": "swarm",
"Driver": "overlay",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "192.168.100.0/24", # 自定義子網(wǎng)
"Gateway": "192.168.100.1" # 自定義網(wǎng)關(guān)
}
]
},
"Internal": false,
"Attachable": true,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": null,
"Options": {
"com.docker.network.driver.overlay.vxlanid_list": "4098"
},
"Labels": null
}
]4.將docker02加入集群
# 獲取加入集群命令
[root@docker01 ~]# docker swarm join-token worker
To add a worker to this swarm, run the following command:
docker swarm join --token SWMTKN-1-1rqzq4jhf4wm77e8yn6s347sd189u84mr0u042kwxxv05n8bbx-1rv4ae95p4e4y6aztlhkvqtfx 192.168.73.128:2377
# 在docker02上執(zhí)行
[root@docker02 ~]# docker swarm join --token SWMTKN-1-1rqzq4jhf4wm77e8yn6s347sd189u84mr0u042kwxxv05n8bbx-1rv4ae95p4e4y6aztlhkvqtfx 192.168.73.128:2377
This node joined a swarm as a worker.
# docker01 上查詢是否加入成功
[root@docker01 ~]# docker node ls
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS ENGINE VERSION
9fn9iyxhkxvjey06lwhgv7zhb * docker01 Ready Active Leader 26.1.4
4m1xin9edttdt1ljxtzy3q2ab docker02 Ready Active 26.1.45.docker01創(chuàng)建容器
[root@docker01 ~]# docker run -d --name=busybox1 --network=my-overlay harbor.linux.com/k8s/busybox:latest /bin/sleep 3600
d8b2749823f570d6c08eccf2df369774323a72628e18e09bc9dfb09735bd00f0
# 查詢?nèi)萜鱥p
[root@docker01 ~]# docker exec -it busybox1 /bin/sh
/ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
14: eth0@if15: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1450 qdisc noqueue
link/ether 02:42:c0:a8:64:02 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.2/24 brd 192.168.100.255 scope global eth0
valid_lft forever preferred_lft forever
16: eth1@if17: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue
link/ether 02:42:ac:12:00:03 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.3/16 brd 172.18.255.255 scope global eth1
valid_lft forever preferred_lft forever
# 查看網(wǎng)絡(luò)，可以發(fā)現(xiàn)有了容器的IP及LB IP
[root@docker01 ~]# docker network inspect my-overlay
[
{
"Name": "my-overlay",
"Id": "ue8rewtwd72difwr86gi5wwsl",
"Created": "2024-10-12T14:15:21.812458427+08:00",
"Scope": "swarm",
"Driver": "overlay",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "192.168.100.0/24",
"Gateway": "192.168.100.1"
}
]
},
"Internal": false,
"Attachable": true,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {
"d8b2749823f570d6c08eccf2df369774323a72628e18e09bc9dfb09735bd00f0": {
"Name": "busybox1",
"EndpointID": "225db615a5d654cd813171ed4d07c7f485b362551507dd18125a4405c45b18fb",
"MacAddress": "02:42:c0:a8:64:02",
"IPv4Address": "192.168.100.2/24",
"IPv6Address": ""
},
"lb-my-overlay": {
"Name": "my-overlay-endpoint",
"EndpointID": "cce907ae37301e39dbd55abcba03e50e562f589f7d08e6c57ace8891d4785747",
"MacAddress": "02:42:c0:a8:64:03",
"IPv4Address": "192.168.100.3/24",
"IPv6Address": ""
}
},
"Options": {
"com.docker.network.driver.overlay.vxlanid_list": "4098"
},
"Labels": {},
"Peers": [
{
"Name": "9fc55aae1502",
"IP": "192.168.73.128"
}
]
}
]6.docker02創(chuàng)建容器
[root@docker02 ~]# docker run -d --name=busybox2 --network=my-overlay harbor.linux.com/k8s/busybox:latest /bin/sleep 3600
3dd7b088c68f0247d312070bc63e15a697d5e8aa198f7bf53450ea96843cc41b
# 查詢?nèi)萜鱥p
[root@docker02 ~]# docker exec -it busybox2 /bin/sh
/ # ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
13: eth0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1450 qdisc noqueue
link/ether 02:42:c0:a8:64:04 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.4/24 brd 192.168.100.255 scope global eth0
valid_lft forever preferred_lft forever
15: eth1@if16: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue
link/ether 02:42:ac:12:00:03 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.3/16 brd 172.18.255.255 scope global eth1
valid_lft forever preferred_lft forever
# 查看網(wǎng)絡(luò)，可以發(fā)現(xiàn)有了容器的IP及LB IP
[root@docker02 ~]# docker network inspect my-overlay
[
{
"Name": "my-overlay",
"Id": "ue8rewtwd72difwr86gi5wwsl",
"Created": "2024-10-12T14:21:11.23116209+08:00",
"Scope": "swarm",
"Driver": "overlay",
"EnableIPv6": false,
"IPAM": {
"Driver": "default",
"Options": null,
"Config": [
{
"Subnet": "192.168.100.0/24",
"Gateway": "192.168.100.1"
}
]
},
"Internal": false,
"Attachable": true,
"Ingress": false,
"ConfigFrom": {
"Network": ""
},
"ConfigOnly": false,
"Containers": {
"3dd7b088c68f0247d312070bc63e15a697d5e8aa198f7bf53450ea96843cc41b": {
"Name": "busybox2",
"EndpointID": "e0b40de6b74e610d1e13318f8420fcaa5b7e8b9bcd9c68f6faaa9931ea72f992",
"MacAddress": "02:42:c0:a8:64:04",
"IPv4Address": "192.168.100.4/24",
"IPv6Address": ""
},
"lb-my-overlay": {
"Name": "my-overlay-endpoint",
"EndpointID": "4fe0523b017be80ce24bddd8b034633f998e36630b100d3a0468ce02ba4e533d",
"MacAddress": "02:42:c0:a8:64:05",
"IPv4Address": "192.168.100.5/24",
"IPv6Address": ""
}
},
"Options": {
"com.docker.network.driver.overlay.vxlanid_list": "4098"
},
"Labels": {},
"Peers": [
{
"Name": "9fc55aae1502",
"IP": "192.168.73.128"
},
{
"Name": "473174a88eb9",
"IP": "192.168.73.129"
}
]
}
] 7.在容器內(nèi)部互相ping對(duì)方
# docker01 ping內(nèi)外網(wǎng)測(cè)試 [root@docker01 ~]# docker exec -it busybox1 /bin/sh / # ping 192.168.100.4 PING 192.168.100.4 (192.168.100.4): 56 data bytes 64 bytes from 192.168.100.4: seq=0 ttl=64 time=1.033 ms 64 bytes from 192.168.100.4: seq=1 ttl=64 time=1.702 ms 64 bytes from 192.168.100.4: seq=2 ttl=64 time=2.209 ms ^C --- 192.168.100.4 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 1.033/1.648/2.209 ms / # ping 192.168.100.5 PING 192.168.100.5 (192.168.100.5): 56 data bytes 64 bytes from 192.168.100.5: seq=0 ttl=64 time=0.897 ms 64 bytes from 192.168.100.5: seq=1 ttl=64 time=1.988 ms 64 bytes from 192.168.100.5: seq=2 ttl=64 time=0.893 ms ^C --- 192.168.100.5 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.893/1.259/1.988 ms / # ping www.baidu.com PING www.baidu.com (182.61.200.7): 56 data bytes 64 bytes from 182.61.200.7: seq=0 ttl=127 time=21.864 ms 64 bytes from 182.61.200.7: seq=1 ttl=127 time=23.486 ms 64 bytes from 182.61.200.7: seq=2 ttl=127 time=23.225 ms ^C --- www.baidu.com ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 21.864/22.858/23.486 ms # docker02 ping內(nèi)外網(wǎng)測(cè)試 [root@docker02 ~]# docker exec -it busybox2 /bin/sh / # ping 192.168.100.2 PING 192.168.100.2 (192.168.100.2): 56 data bytes 64 bytes from 192.168.100.2: seq=0 ttl=64 time=1.001 ms 64 bytes from 192.168.100.2: seq=1 ttl=64 time=1.374 ms 64 bytes from 192.168.100.2: seq=2 ttl=64 time=1.990 ms ^C --- 192.168.100.2 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 1.001/1.455/1.990 ms / # ping 192.168.100.3 PING 192.168.100.3 (192.168.100.3): 56 data bytes 64 bytes from 192.168.100.3: seq=0 ttl=64 time=0.572 ms 64 bytes from 192.168.100.3: seq=1 ttl=64 time=0.999 ms 64 bytes from 192.168.100.3: seq=2 ttl=64 time=1.199 ms ^C --- 192.168.100.3 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.572/0.923/1.199 ms / # ping www.baidu.com PING www.baidu.com (182.61.200.6): 56 data bytes 64 bytes from 182.61.200.6: seq=0 ttl=127 time=22.134 ms 64 bytes from 182.61.200.6: seq=1 ttl=127 time=22.375 ms 64 bytes from 182.61.200.6: seq=2 ttl=127 time=22.372 ms ^C --- www.baidu.com ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 22.134/22.293/22.375 ms # Overlay網(wǎng)絡(luò)ping通內(nèi)外網(wǎng)的原理 # 內(nèi)部網(wǎng)絡(luò)通信： 1.在Overlay網(wǎng)絡(luò)中，虛擬機(jī)之間的通信通過(guò)虛擬隧道進(jìn)行。每個(gè)虛擬機(jī)都有一個(gè)唯一的IP地址，這個(gè)地址在Overlay網(wǎng)絡(luò)中有效。 2.當(dāng)一個(gè)虛擬機(jī)需要向另一個(gè)虛擬機(jī)發(fā)送數(shù)據(jù)時(shí)，數(shù)據(jù)會(huì)被封裝在Overlay報(bào)文中，并通過(guò)虛擬隧道傳輸?shù)侥繕?biāo)虛擬機(jī)。 3.由于Overlay網(wǎng)絡(luò)是在物理網(wǎng)絡(luò)之上構(gòu)建的，因此虛擬機(jī)之間的通信不會(huì)受到物理網(wǎng)絡(luò)細(xì)節(jié)的影響。 # 外部網(wǎng)絡(luò)通信： 1.Overlay網(wǎng)絡(luò)通常與物理網(wǎng)絡(luò)相連，以便虛擬機(jī)能夠訪問(wèn)外部網(wǎng)絡(luò)。 2.在這種情況下，虛擬機(jī)發(fā)出的數(shù)據(jù)會(huì)被封裝在Overlay報(bào)文中，并通過(guò)物理網(wǎng)絡(luò)的網(wǎng)關(guān)或路由器發(fā)送到外部網(wǎng)絡(luò)。 3.外部網(wǎng)絡(luò)收到的數(shù)據(jù)會(huì)被解封裝，并根據(jù)目標(biāo)IP地址進(jìn)行路由和轉(zhuǎn)發(fā)。
VXLAN（Virtual eXtensible Local Area Network）是一種網(wǎng)絡(luò)虛擬化技術(shù)，它使用隧道協(xié)議將二層以太網(wǎng)幀封裝在三層IP報(bào)文中，從而實(shí)現(xiàn)跨物理網(wǎng)絡(luò)的二層連接。這里的vxlan:vethXXX表示通過(guò)VXLAN隧道連接的虛擬以太網(wǎng)接口，它可能用于將容器的流量封裝并通過(guò)宿主機(jī)發(fā)送到外部網(wǎng)絡(luò)或其他容器。vxlan才是實(shí)體，overlay只是網(wǎng)絡(luò)模型；一句話就是vxlan是overlay網(wǎng)絡(luò)的一種實(shí)現(xiàn)。
到此這篇關(guān)于Docker 容器跨主機(jī)通信 overlay的文章就介紹到這了,更多相關(guān)Docker 容器跨主機(jī)通信內(nèi)容請(qǐng)搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家！
您可能感興趣的文章:
- 在Docker容器之間如何進(jìn)行通信
- Docker網(wǎng)絡(luò)配置與自定義IP容器通信
- Docker 容器之間的互相通信實(shí)現(xiàn)示例
- Docker容器跨主機(jī)通信overlay網(wǎng)絡(luò)的解決方案
- Docker容器之間的通信的方法實(shí)現(xiàn)
- Docker容器間通信與外網(wǎng)通信的操作
- Docker容器連接相互通信的實(shí)現(xiàn)
- 詳解Docker 容器跨主機(jī)多網(wǎng)段通信解決方案
- Docker跨主機(jī)容器通信overlay實(shí)現(xiàn)過(guò)程詳解
- 詳解Docker容器跨主機(jī)通信的方法
- docker多個(gè)容器的相互通信實(shí)現(xiàn)步驟
相關(guān)文章
解決Docker鏡像拉取超時(shí)及優(yōu)化網(wǎng)絡(luò)配置的方法(failed to do request
在使用 Docker 構(gòu)建和部署應(yīng)用時(shí),拉取鏡像是一個(gè)關(guān)鍵的步驟,然而,在一些網(wǎng)絡(luò)環(huán)境中,特別是企業(yè)內(nèi)部網(wǎng)或受限網(wǎng)絡(luò)環(huán)境中,可能會(huì)遇到 Docker 鏡像拉取失敗或超時(shí)的問(wèn)題,這篇博客將詳細(xì)探討如何應(yīng)對(duì) Docker 鏡像拉取超時(shí)的問(wèn)題,需要的朋友可以參考下2024-11-11
Docker數(shù)據(jù)卷掛載命令volume(-v)與mount的使用總結(jié)
本文主要介紹了Docker數(shù)據(jù)卷掛載命令volume(-v)與mount的使用總結(jié)，文中通過(guò)示例代碼介紹的非常詳細(xì)，對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值，需要的朋友們下面隨著小編來(lái)一起學(xué)習(xí)學(xué)習(xí)吧2022-08-08
本文詳細(xì)介紹了如何在Docker中使用Jenkins,包括Jenkins的基本概念、準(zhǔn)備工作、下載和運(yùn)行Jenkins、通過(guò)docker-compose部署Jenkins以及更新Jenkins的步驟2024-11-11
這篇文章主要介紹了Docker service命令詳解(小結(jié))，小編覺(jué)得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過(guò)來(lái)看看吧2018-08-08
docker打包鏡像后EasyExcel報(bào)錯(cuò),dockerfile缺少字體的解決
解決Docker打包鏡像后EasyExcel報(bào)錯(cuò)的問(wèn)題：1. Dockerfile增加字體配置；2. 使用EasyExcel的write時(shí)添加"inMemory"參數(shù)為true,開(kāi)啟內(nèi)存處理模式（不推薦,1W數(shù)據(jù)以內(nèi)可以考慮）2025-02-02
centos6使用docker部署kafka項(xiàng)目的方法分析
這篇文章主要介紹了centos6使用docker部署kafka項(xiàng)目的方法,結(jié)合實(shí)例形式分析了centos6環(huán)境下使用docker部署kafka項(xiàng)目的相關(guān)命令與使用技巧,需要的朋友可以參考下2020-02-02
解決docker run中使用 ./ 相對(duì)路徑掛載文件或目錄失敗的問(wèn)題
這篇文章主要介紹了解決docker run中使用‘./‘相對(duì)路徑掛載文件或目錄失敗的問(wèn)題，具有很好的參考價(jià)值，希望對(duì)大家有所幫助。一起跟隨小編過(guò)來(lái)看看吧2021-03-03
本文詳細(xì)介紹了如何修改Docker配置文件以使用私有倉(cāng)庫(kù),并解決相關(guān)問(wèn)題,包括配置文件的編輯、DNS設(shè)置、證書(shū)管理以及系統(tǒng)時(shí)間同步2025-03-03
Docker中部署Mino并掛載配置文件的項(xiàng)目實(shí)踐
本文主要介紹了Docker中部署Mino并掛載配置文件的項(xiàng)目實(shí)踐，文中通過(guò)示例代碼介紹的非常詳細(xì)，對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值，需要的朋友們下面隨著小編來(lái)一起學(xué)習(xí)學(xué)習(xí)吧2023-06-06
這篇文章主要介紹了Docker的基本命令使用筆記，小編覺(jué)得挺不錯(cuò)的，現(xiàn)在分享給大家，也給大家做個(gè)參考。一起跟隨小編過(guò)來(lái)看看吧2018-06-06