注:本文是本人根据B站【狂神说Java】Docker视频所写,仅供学习参考。
Docker 网络
理解Docker0
清空所有环境
# 删除所有容器
docker rm -f $(docker ps -aq)
# 删除所有镜像
docker rmi -f $(docker images -aq)
测试
[root@localhost ~]# ip addr
-bash: ip: command not found
[root@localhost /]# yum -y install initscripts
[root@localhost /]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:4e:a2:d7 brd ff:ff:ff:ff:ff:ff
inet 192.168.28.65/24 brd 192.168.28.255 scope global dynamic ens33
valid_lft 40973sec preferred_lft 40973sec
inet6 fe80::70f9:937c:a565:5e11/64 scope link
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:75:84:73:29 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
# 三个网络
# 问题 docker是如何处理容器网络访问的?
# [root@localhost /]# docker run -d -P --name tomcat01 tomcat
# 查看容器的内部网络地址 ip addr 发现容器启动的时候回得到一个 eth0@if5 ip地址 docker分配的!
[root@localhost /]# docker exec -it tomcat01 ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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
4: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0
valid_lft forever preferred_lft forever
# 思考 linux 能不能 ping 通 容器内部
[root@localhost /]# ping 172.17.0.2
PING 172.17.0.2 (172.17.0.2) 56(84) bytes of data.
64 bytes from 172.17.0.2: icmp_seq=1 ttl=64 time=0.137 ms
64 bytes from 172.17.0.2: icmp_seq=2 ttl=64 time=0.088 ms
64 bytes from 172.17.0.2: icmp_seq=3 ttl=64 time=0.056 ms
# linux 可以 ping 通docker容器内部
原理
1、我们每启动一个docker容器,docker就会给docker容器分配一个ip,我们只要安装了docker,就会有一个网卡docker0 桥接模式使用的技术是evth-pair 技术!
再次测试 ip addr
2、再启动一个容器测试 发现又多了一对网卡!
[root@localhost /]# docker run -d -P --name tomcat02 tomcat
701eb44ebc57fe3e251f9ccdbea043716a1205f526dfc25135cb92a9f7661a21
[root@localhost /]# ip addr
# 我们发现这个容器带来的网卡,都是一对一对的
# evth-pair 就是一对的虚拟设备接口,他们是成对出现的,一端连着协议,一端彼此相连
# 正因为有这个特性,evth-pair 充当一个桥梁 连接各种虚拟网络设备
# OpenStac,Docker容器之间的连接,OVS的连接,都是使用evth-pair技术
3、我们来测试下 tomcat01 和 tomcat02 能否ping通
[root@localhost /]# docker exec -it tomcat01 ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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
4: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0
valid_lft forever preferred_lft forever
[root@localhost /]# docker exec -it tomcat02 ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
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
6: eth0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0
valid_lft forever preferred_lft forever
[root@localhost /]# docker exec -it tomcat01 ping 172.17.0.3
PING 172.17.0.3 (172.17.0.3) 56(84) bytes of data.
64 bytes from 172.17.0.3: icmp_seq=1 ttl=64 time=0.209 ms
64 bytes from 172.17.0.3: icmp_seq=2 ttl=64 time=0.134 ms
64 bytes from 172.17.0.3: icmp_seq=3 ttl=64 time=0.095 ms
# 结论容器和容器之间是可以互相ping通的!
结论:tomcat01 和tomcat02 是公用一个路由器 docker0
所有的容器不指定网络的情况下,都是docker0路由的,docker会给容器分配一个默认的可用IP
小结
Docker使用的是Linux的桥接,宿主机中是一个Docker容器的网桥 docker0
Docker中的所有的网络接口都是虚拟的,虚拟的转发效率高!
只要容器删除,对应网桥一对就没了!
–link
思考一个场景,我们编写了一个微服务 database url = ip 项目不重启 数据库ip换掉了,我们希望可以处理这个问题,可以通过名字来进行访问容器?
[root@localhost /]# docker exec -it tomcat02 ping tomcat01
ping: tomcat01: No address associated with hostname
#如何解决?
#通过 --link 可以解决网络连通问题
[root@localhost /]# docker run -d -P --name tomcat03 --link tomcat02 tomcat
e9fbd03349eec4464aa63a7f800aa889e076ebb5b7cde5257c78384a964ef031
[root@localhost /]# docker exec -it tomcat03 ping tomcat02
PING tomcat02 (172.17.0.3) 56(84) bytes of data.
64 bytes from tomcat02 (172.17.0.3): icmp_seq=1 ttl=64 time=0.218 ms
64 bytes from tomcat02 (172.17.0.3): icmp_seq=2 ttl=64 time=0.077 ms
64 bytes from tomcat02 (172.17.0.3): icmp_seq=3 ttl=64 time=0.074 ms
[root@localhost /]# docker exec -it tomcat02 ping tomcat03
ping: tomcat03: No address associated with hostname
探究:inspect
[root@localhost /]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e9fbd03349ee tomcat "catalina.sh run" 12 minutes ago Up 12 minutes 0.0.0.0:32771->8080/tcp tomcat03
701eb44ebc57 tomcat "catalina.sh run" 39 minutes ago Up 39 minutes 0.0.0.0:32769->8080/tcp tomcat02
0833debd3d7c tomcat "catalina.sh run" 48 minutes ago Up 48 minutes 0.0.0.0:32768->8080/tcp tomcat01
[root@localhost /]# docker inspect e9fbd03349ee
# 发现tomcat03 和 tomcat02 联系
其实这个tomcat03就是在本地配置了tomcat02的配置!
# 查看hosts 配置
[root@localhost /]# docker exec -it tomcat03 cat /etc/hosts
127.0.0.1 localhost
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
172.17.0.3 tomcat02 701eb44ebc57
172.17.0.4 e9fbd03349ee
# 本质探究 --link 就是我们在hosts配置中添加了一个172.17.0.3 tomcat02 701eb44ebc57
我们现在玩Docker 已经不建议使用–link了!
自定义网络!不适用docker0!
docker0问题:不支持容器名连接访问!
自定义网络
#查了所有docker网络
[root@localhost /]# docker network ls
NETWORK ID NAME DRIVER SCOPE
9b3fe77c32b4 bridge bridge local
9424102af469 host host local
06c9c2b6a2ac none null local
网络模式
# bridge:桥接 docker 搭桥 (默认)
# none:不配置网络
# host:和宿主机共享网络
# container:容器网络连通!(用的少,局限很大)
测试
# 我们直接启动的命令 --net bridge 而这个就是我们的docker0
# docker0特点,默认,域名不能访问
# 这两个方式启动效果相同
docker run -d -P --name tomcat01 tomcat
docker run -d -P --name tomcat01 --net bridge tomcat
# 我们可以自定义一个网络!
# --driver bridge (桥接)
# --subnet 192.168.0.0/16 (子网地址)
# --gateway 192.168.0.1 (网关)
[root@localhost /]# docker network create --driver bridge --subnet 192.168.0.0/16 --gateway 192.168.0.1 mynet
252386dce4b5911b6d52e3132b2387d64d2a14dd33819d426133743752a447df
[root@localhost /]# docker network ls
NETWORK ID NAME DRIVER SCOPE
9b3fe77c32b4 bridge bridge local
9424102af469 host host local
252386dce4b5 mynet bridge local
06c9c2b6a2ac none null local
# 我们自己的网络就创建好了
# 启动两个指定网络--net mynet 的容器
[root@localhost /]# docker run -d -P --name tomcat-net-01 --net mynet tomcat
c4f15146de5e06e962ed0543ff43121dde97d9e84e469badb0554db8350d1460
[root@localhost /]# docker run -d -P --name tomcat-net-02 --net mynet tomcat
d3d79b0db98be3620a313be7f4d922073097512a175b20ad63950dcf38514db2
[root@localhost /]# docker network inspect mynet
[
{
"Name": "mynet",
"Id": "252386dce4b5911b6d52e3132b2387d64d2a14dd33819d426133743752a447df",
"Created": "2020-11-14T02:13:39.336201549-05: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": {
"c4f15146de5e06e962ed0543ff43121dde97d9e84e469badb0554db8350d1460": {
"Name": "tomcat-net-01",
"EndpointID": "f5d7972a1e7fea6880c14b388c3b5140a5d124b1ca26206c4679d925d791486a",
"MacAddress": "02:42:c0:a8:00:02",
"IPv4Address": "192.168.0.2/16",
"IPv6Address": ""
},
"d3d79b0db98be3620a313be7f4d922073097512a175b20ad63950dcf38514db2": {
"Name": "tomcat-net-02",
"EndpointID": "26b5f305486aa9bbcba379fb714f67319b18cc9fbc5d7cfd4371cf8f3f648306",
"MacAddress": "02:42:c0:a8:00:03",
"IPv4Address": "192.168.0.3/16",
"IPv6Address": ""
}
},
"Options": {},
"Labels": {}
}
]
# 再次测试ping连接
[root@localhost /]# docker exec -it tomcat-net-01 ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.113 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.199 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.110 ms
# 不使用--link 也可以通过名字ping通
[root@localhost /]# docker exec -it tomcat-net-01 ping tomcat-net-02
PING tomcat-net-02 (192.168.0.3) 56(84) bytes of data.
64 bytes from tomcat-net-02.mynet (192.168.0.3): icmp_seq=1 ttl=64 time=0.308 ms
64 bytes from tomcat-net-02.mynet (192.168.0.3): icmp_seq=2 ttl=64 time=0.117 ms
64 bytes from tomcat-net-02.mynet (192.168.0.3): icmp_seq=3 ttl=64 time=0.127 ms
我们自定义的网络docker都已经帮我们维护好了对应的关系,推荐我们平时这样使用网络!
好处:
redis – 不同的集群使用不同的网络,保证集群是安全和健康的!
mysql – 不同的集群使用不同的网络,保证集群是安全和健康的!
网络连通
# 启动两个默认容器
[root@localhost /]# docker run -d -P --name tomcat01 tomcat
4c885855a358af727690216694f76d8262bdc1185e04c5dd6b6384df862ea238
[root@localhost /]# docker run -d -P --name tomcat02 tomcat
a11fd6c6fac57f17dcc409fd878551f1caa5e328f9752464614631778894dd30
#测试是否可以ping通指定网络 mynet 的容器
[root@localhost /]# docker exec -it tomcat01 ping tomcat-net-01
ping: tomcat-net-01: No address associated with hostname
# 测试打通tomcat01 到 mynet
[root@localhost /]# docker network connect mynet tomcat01
# 连通之后就是将tomcat01 放到了mynet网络下!
# 一个容器两个IP
# 再次测试是否可以ping通 成功 tomcat01 可以连通
[root@localhost /]# docker exec -it tomcat01 ping tomcat-net-01
PING tomcat-net-01 (192.168.0.2) 56(84) bytes of data.
64 bytes from tomcat-net-01.mynet (192.168.0.2): icmp_seq=1 ttl=64 time=0.222 ms
64 bytes from tomcat-net-01.mynet (192.168.0.2): icmp_seq=2 ttl=64 time=0.101 ms
64 bytes from tomcat-net-01.mynet (192.168.0.2): icmp_seq=3 ttl=64 time=0.071 ms
# tomcat02 无法连通 如果想要连通需要按照tomcat01 操作再进行配置
[root@localhost /]# docker exec -it tomcat02 ping tomcat-net-01
ping: tomcat-net-01: No address associated with hostname
结论:假设要跨网络操作别人,就需要使用docker network connect 连通!