扫码关注官方微信

扫码下载APP
返回顶部
首页 > 资讯 > 移动开发 >docker网络配置过程详解介绍
  • 345

0
分享到

docker网络配置过程详解介绍

2024-04-02 19:04:59 345人浏览 泡泡鱼
摘要

目录linux内核实现名称空间的创建操作Network Namespace创建veth pair实现Network Namespace间通信四种网络模式配置容器的常用操作自定义Doc

Linux内核实现名称空间的创建

ip netns命令

可以借助ip netns命令来完成对 Network Namespace 的各种操作。ip netns命令来自于iproute安装包，一般系统会默认安装，如果没有的话，请自行安装。

注意：ip netns命令修改网络配置时需要 sudo 权限。

可以通过ip netns命令完成对Network Namespace 的相关操作，可以通过ip netns help查看命令帮助信息：


[root@master ~]# ip netns help
Usage:  ip netns list
        ip netns add NAME
        ip netns attach NAME PID
        ip netns set NAME NETNSID
        ip [-all] netns delete [NAME]
        ip netns identify [PID]
        ip netns pids NAME
        ip [-all] netns exec [NAME] cmd ...
        ip netns monitor
        ip netns list-id [target-nsid POSITIVE-INT] [nsid POSITIVE-INT]
NETNSID := auto | POSITIVE-INT
[root@master ~]# ip netns list
[root@master ~]# ip netns add ns0
[root@master ~]# ip netns list
ns0
[root@master ~]# ls /var/run/netns
ns0
[root@master ~]# ip netns add ns0
Cannot create namespace file "/var/run/netns/ns0": File exists
[root@master ~]# touch /var/run/netns/ns1
[root@master ~]# ip netns list
Error: Peer netns reference is invalid.
Error: Peer netns reference is invalid.
ns1
ns0
[root@master ~]# ip netns del ns1
[root@master ~]# ip netns list
ns0

操作Network Namespace

ip命令提供了ip netns exec子命令可以在对应的 Network Namespace 中执行命令。

查看新创建 Network Namespace 的网卡信息


[root@master ~]# ip netns exec ns0 ip addr
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
可以看到，新创建的Network Namespace中会默认创建一个lo回环网卡，此时网卡处于关闭状态。此时，尝试去 ping 该lo回环网卡，会提示Network is unreachable
[root@master ~]# ip netns exec ns0 ping 127.0.0.1
connect: 网络不可达
通过下面的命令启用lo回环网卡
[root@master ~]# ip netns exec ns0 ip link set lo up
[root@master ~]# ip netns exec ns0 ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.024 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.019 ms

转移设备

我们可以在不同的 Network Namespace 之间转移设备（如veth）。由于一个设备只能属于一个 Network Namespace ，所以转移后在这个 Network Namespace 内就看不到这个设备了。

其中，veth设备属于可转移设备，而很多其它设备（如lo、vxlan、ppp、bridge等）是不可以转移的。

veth pair

veth pair 全称是 Virtual Ethernet Pair，是一个成对的端口，所有从这对端口一 端进入的数据包都将从另一端出来，反之也是一样。

引入veth pair是为了在不同的 Network Namespace 直接进行通信，利用它可以直接将两个 Network Namespace 连接起来。

在这里插入图片描述

创建veth pair


[root@master ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:d7:ce:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.197.131/24 brd 192.168.197.255 scope global dynamic noprefixroute ens33
       valid_lft 1522sec preferred_lft 1522sec
    inet6 fe80::1f2f:a9f9:78a7:7cc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:b8:38:aa:7d 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
    inet6 fe80::42:b8ff:fe38:aa7d/64 scope link 
       valid_lft forever preferred_lft forever
7: veth2672252@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether ca:56:6c:07:de:af brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::c856:6cff:fe07:deaf/64 scope link 
       valid_lft forever preferred_lft forever
[root@master ~]# ip link add type veth
[root@master ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:d7:ce:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.197.131/24 brd 192.168.197.255 scope global dynamic noprefixroute ens33
       valid_lft 1499sec preferred_lft 1499sec
    inet6 fe80::1f2f:a9f9:78a7:7cc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:b8:38:aa:7d 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
    inet6 fe80::42:b8ff:fe38:aa7d/64 scope link 
       valid_lft forever preferred_lft forever
7: veth2672252@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether ca:56:6c:07:de:af brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::c856:6cff:fe07:deaf/64 scope link 
       valid_lft forever preferred_lft forever
10: veth0@veth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a2:0f:68:39:2c:fd brd ff:ff:ff:ff:ff:ff
11: veth1@veth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether e6:e9:55:96:60:35 brd ff:ff:ff:ff:ff:ff

可以看到，此时系统中新增了一对veth pair，将veth0和veth1两个虚拟网卡连接了起来，此时这对 veth pair 处于”未启用“状态。

实现Network Namespace间通信


[root@master ~]#  ip netns list
ns0
[root@master ~]# ip netns add ns1
[root@master ~]# ip link set veth0 netns ns0
[root@master ~]# ip link set veth1 netns ns1
[root@master ~]# ip netns exec ns0 ip link set veth0 up
[root@master ~]# ip netns exec ns0 ip addr add 192.168.2.1/24 dev veth0
[root@master ~]# ip netns exec ns1 ip link set veth1 up
[root@master ~]# ip netns exec ns1  ip addr add 192.168.2.2/24 dev veth1
[root@master ~]# ip netns exec ns0 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
10: veth0@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:0f:68:39:2c:fd brd ff:ff:ff:ff:ff:ff link-netns ns1
    inet 192.168.2.1/24 scope global veth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a00f:68ff:fe39:2cfd/64 scope link 
       valid_lft forever preferred_lft forever
[root@master ~]# ip netns exec ns1 ip a
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
11: veth1@if10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e6:e9:55:96:60:35 brd ff:ff:ff:ff:ff:ff link-netns ns0
    inet 192.168.2.2/24 scope global veth1
       valid_lft forever preferred_lft forever
    inet6 fe80::e4e9:55ff:fe96:6035/64 scope link 
       valid_lft forever preferred_lft forever
[root@master ~]# ip netns exec ns1 ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.037 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.028 ms

可以看到，veth pair成功实现了两个不同Network Namespace之间的网络交互。

veth设备重命名


[root@master ~]# ip netns exec ns0 ip link set veth0 down
[root@master ~]# ip netns exec ns0 ip link set veth0 down
[root@master ~]# ip netns exec ns0 ip link set veth0 down
[root@master ~]# ip netns exec ns0 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
10: veth0@if11: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether a2:0f:68:39:2c:fd brd ff:ff:ff:ff:ff:ff link-netns ns1
    inet 192.168.2.1/24 scope global veth0
       valid_lft forever preferred_lft forever
[root@master ~]# ip netns exec ns1 ip link set veth1 down 
[root@master ~]# ip netns exec ns1 ip link  set dev veth1 name eth0
[root@master ~]# ip netns exec ns1 ip link set eth0
[root@master ~]# ip netns exec ns1 ip a
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
11: eth0@if10: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether e6:e9:55:96:60:35 brd ff:ff:ff:ff:ff:ff link-netns ns0
    inet 192.168.2.2/24 scope global eth0
       valid_lft forever preferred_lft forever

四种网络模式配置

bridge模式


[root@master ~]# docker pull busybox
Using default tag: latest
latest: Pulling from library/busybox
3aab638df1a9: Pull complete 
Digest: sha256:52817dece4cfe26f581c834d27a8e1bcc82194f914afe6d50afad5a101234ef1
Status: Downloaded newer image for busybox:latest
docker.io/library/busybox:latest
[root@master ~]# docker run -it --name b1 --rm busybox # --rm 删除或停止容器后自动销毁容器
/ # 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
12: eth0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0
       valid_lft forever preferred_lft forever
/ # exit
[root@master ~]# docker run -it --name b1 --network bridge --rm busybox
/ # 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
14: eth0@if15: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0
       valid_lft forever preferred_lft forever
/ # exit

none模式


[root@master ~]# docker run -it --name b2 --rm --network none busybox
/ # 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
/ # exit
使用none模式，Docker容器拥有自己的Network Namespace，但是，并不为Docker容器进行任何网络配置。也就是说，这个Docker容器没有网卡、IP、路由等信息。需要我们自己为Docker容器添加网卡、配置IP等。

container模式


[root@master ~]# docker run -it --name b3 --rm busybox
/ #  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
16: eth0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0
       valid_lft forever preferred_lft forever
新开一个终端
[root@master ~]# docker run -it --name b4 --rm --network container:b3 busybox
/ # 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
16: eth0@if17: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0
       valid_lft forever preferred_lft forever
 在b3上创建一个文件
/ # ls
bin   dev   etc   home  proc  root  sys   tmp   usr   var
/ # mkdir yy
在b4上查看
/ # ls
bin   dev   etc   home  proc  root  sys   tmp   usr   var
在b3上创建网站
/ # echo "aaa." > bbb/index.html
/ # Httpd -h bbb/
/ # netstat -antl
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 :::80                   :::*                    LISTE

# 在b4上访问
/ # wget -qO - 172.17.0.2
aaa
/ #
# 由此可见，container模式下的容器间关系就相当于一台主机上的两个不同进程

这个模式指定新创建的容器和已经存在的一个容器共享一个 Network Namespace，而不是和宿主机共享。新创建的容器不会创建自己的网卡，配置自己的 IP，而是和一个指定的容器共享 IP、端口范围等。同样，两个容器除了网络方面，其他的如文件系统、进程列表等还是隔离的。两个容器的进程可以通过 lo 网卡设备通信。

host模式
启动容器时直接指明模式为host


[root@master ~]# docker run -it --name b5 --rm --network host busybox
/ # 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
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel qlen 1000
    link/ether 00:0c:29:d7:ce:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.197.131/24 brd 192.168.197.255 scope global dynamic noprefixroute ens33
       valid_lft 1741sec preferred_lft 1741sec
    inet6 fe80::1f2f:a9f9:78a7:7cc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
    link/ether 02:42:b8:38:aa:7d 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
    inet6 fe80::42:b8ff:fe38:aa7d/64 scope link 
       valid_lft forever preferred_lft forever
7: veth2672252@if6: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master docker0 
    link/ether ca:56:6c:07:de:af brd ff:ff:ff:ff:ff:ff
    inet6 fe80::c856:6cff:fe07:deaf/64 scope link 
       valid_lft forever preferred_lft forever
/ # mkdir www
/ # echo "ccc" > www/index.html
/ # httpd -h www/
/ # 
[root@master ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:d7:ce:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.197.131/24 brd 192.168.197.255 scope global dynamic noprefixroute ens33
       valid_lft 1730sec preferred_lft 1730sec
    inet6 fe80::1f2f:a9f9:78a7:7cc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:b8:38:aa:7d 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
    inet6 fe80::42:b8ff:fe38:aa7d/64 scope link 
       valid_lft forever preferred_lft forever
7: veth2672252@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
    link/ether ca:56:6c:07:de:af brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::c856:6cff:fe07:deaf/64 scope link 
       valid_lft forever preferred_lft forever
[root@master ~]# curl 192.168.197.131
ccc

容器的常用操作


[root@master ~]# docker run -it --name b6 --rm busybox
/ # hostname
ef156ee78b70
/ # exit
[root@master ~]# docker run -it --name b6 --hostname yanghaixx busybox
/ # hostname 
yanghaixx
/ # 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      yanghaixx
/ # cat /etc/resolv.conf 
# Generated by NetworkManager
search localdomain
nameserver 192.168.197.2
/ # ping baidu.com
PING baidu.com (220.181.38.148): 56 data bytes
64 bytes from 220.181.38.148: seq=0 ttl=127 time=25.224 ms
64 bytes from 220.181.38.148: seq=1 ttl=127 time=24.795 ms
[root@master ~]# docker run -it --rm  --name b7 --dns 8.8.8.8 --hostname yanghaixx busybox
/ # cat /etc/resolv.conf 
search localdomain
nameserver 8.8.8.8

/ # exit .
[root@master ~]# docker run -it --name b7 --rm --hostname yanghaixx --add-host baidu.com:0.0.0.0  busybox
/ # 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
0.0.0.0 baidu.com
172.17.0.3      yanghaixx

端口映射
执行docker run的时候有个-p选项，可以将容器中的应用端口映射到宿主机中，从而实现让外部主机可以通过访问宿主机的某端口来访问容器内应用的目的。


-p选项能够使用多次，其所能够暴露的端口必须是容器确实在监听的端口。

-p选项的使用格式：

-p
将指定的容器端口映射至主机所有地址的一个动态端口
动态端口指的是随机端口，具体的映射结果可使用docker port命令查看。


[root@master ~]# docker run -d --name WEB1 --rm -p 80 yanghaixx/Nginx:v2
62029a5977a06e07ab5b40c78ce60e9cc519364512bc2e6d5785afd7dc1e090f
[root@master ~]#  docker port web1
80/tcp -> 0.0.0.0:49153
80/tcp -> :::49153
[root@master ~]# curl 192.168.197.131:49153
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

将容器端口映射到宿主机的指定端口


[root@master ~]# docker run -itd --name web2 --rm -p 2525:80 yanghaixx/nginx:v2
62a93a8ef40eec981b2d1682da92523027999991b0294782be38d4565b210ff8
[root@master ~]# docker port web2
80/tcp -> 0.0.0.0:2525
80/tcp -> :::2525
[root@master ~]# curl 192.168.197.131:2525
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

自定义docker0桥的网络属性信息

自定义docker0桥的网络属性信息需要修改/etc/docker/daemon.JSON配置文件


[root@master ~]# vim /etc/docker/daemon.json
[root@master ~]# cat /etc/docker/daemon.json
{
        "reGIStry-mirrors": ["https://q9u587gb.mirror.aliyuncs.com"]
        "bip": "192.168.2.1/24"
}
See "systemctl status docker.service" and "journalctl -xe" for details.
[root@master ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:d7:ce:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.197.131/24 brd 192.168.197.255 scope global dynamic noprefixroute ens33
       valid_lft 1690sec preferred_lft 1690sec
    inet6 fe80::1f2f:a9f9:78a7:7cc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:97:2a:95:42 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.1/24 brd 192.168.2.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:97ff:fe2a:9542/64 scope link 
       valid_lft forever preferred_lft forever

docker创建自定义桥


[root@master ~]# vim /etc/docker/daemon.json
[root@master ~]# cat /etc/docker/daemon.json
{
        "registry-mirrors": ["https://q9u587gb.mirror.aliyuncs.com"]
        "bip": "192.168.2.1/24"
}
See "systemctl status docker.service" and "journalctl -xe" for details.
[root@master ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 00:0c:29:d7:ce:07 brd ff:ff:ff:ff:ff:ff
    inet 192.168.197.131/24 brd 192.168.197.255 scope global dynamic noprefixroute ens33
       valid_lft 1690sec preferred_lft 1690sec
    inet6 fe80::1f2f:a9f9:78a7:7cc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:f1:42:78 brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:97:2a:95:42 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.1/24 brd 192.168.2.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:97ff:fe2a:9542/64 scope link 
       valid_lft forever preferred_lft forever

使用新创建的自定义桥来创建容器：


[root@master ~]# docker run -itd --name web --network br0 --rm yanghaixx/nginx:v2
aec728f703567b36016cf09cde1ffd1036673D7c2d961cae0b81cd09721d5cb9
[root@master ~]# docker exec -it web /bin/bash
[root@aec728f70356 /]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
31: eth0@if32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:ac:11:01:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.17.1.2/24 brd 172.17.1.255 scope global eth0
       valid_lft forever preferred_lft forever

再创建一个容器，使用默认的bridge桥：


[root@master ~]# docker run -itd --name web02 --rm luojiatian1904/nginx:v2
4ee412be6d20b96a18f0b6fc0062beefc2192d906b212134b362ec41be5144ff
[root@master ~]# docker exec -it web02 /bin/bash
[root@4ee412be6d20 /]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
33: eth0@if34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:c0:a8:02:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 192.168.2.2/24 brd 192.168.2.255 scope global eth0
       valid_lft forever preferred_lft forever
[root@4ee412be6d20 /]#

试想一下，此时的b2与b1能否互相通信？如果不能该如何实现通信


# 运行两个容器在不同网段
[root@master ~]# docker run -itd --name web --network br0 --rm yanghaixx/nginx:v2
aec728f703567b36016cf09cde1ffd1036673d7c2d961cae0b81cd09721d5cb9
[root@master ~]# docker exec -it web /bin/bash
[root@aec728f70356 /]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
31: eth0@if32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:ac:11:01:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.17.1.2/24 brd 172.17.1.255 scope global eth0
       valid_lft forever preferred_lft forever

[root@master ~]# docker run -itd --name web02 --rm yanghaixx/nginx:v2
4ee412be6d20b96a18f0b6fc0062beefc2192d906b212134b362ec41be5144ff
[root@master ~]# docker exec -it web02 /bin/bash
[root@4ee412be6d20 /]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
33: eth0@if34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:c0:a8:02:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 192.168.2.2/24 brd 192.168.2.255 scope global eth0
       valid_lft forever preferred_lft forever


[root@master ~]# docker ps -a
CONTAINER ID   IMAGE                     COMMAND                  CREATED         STATUS         PORTS     NAMES
4ee412be6d20   luojiatian1904/nginx:v2   "/usr/local/nginx/sb…"   2 minutes aGo   Up 2 minutes             web02
aec728f70356   luojiatian1904/nginx:v2   "/usr/local/nginx/sb…"   2 minutes ago   Up 2 minutes             web

将br0网络 (C1) 连接到c2(一个容器运行两个桥)


[root@master ~]# docker network connect  br0 aec728f70356(web容器ID)
[root@4ee412be6d20 /]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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
33: eth0@if34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:c0:a8:02:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 192.168.2.2/24 brd 192.168.2.255 scope global eth0
       valid_lft forever preferred_lft forever
35: eth1@if36: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:ac:11:01:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 172.17.1.3/24 brd 172.17.1.255 scope global eth1
       valid_lft forever preferred_lft forever

[root@4ee412be6d20 /]# ping 172.17.1.2
PING 172.17.1.2 (172.17.1.2) 56(84) bytes of data.
64 bytes from 172.17.1.2: icmp_seq=1 ttl=64 time=0.095 ms

到此这篇关于docker网络配置过程详解介绍的文章就介绍到这了,更多相关docker网络配置内容请搜索编程网以前的文章或继续浏览下面的相关文章希望大家以后多多支持编程网！

--结束END--

本文标题: docker网络配置过程详解介绍

本文链接: https://lsjlt.com/news/159451.html(转载时请注明来源链接)

有问题或投稿请发送至: 邮箱/279061341@qq.com    QQ/279061341

猜你喜欢
  • docker网络配置过程详解介绍
    目录Linux内核实现名称空间的创建操作Network Namespace创建veth pair实现Network Namespace间通信四种网络模式配置容器的常用操作自定义doc...
    99+
    2024-04-02
  • Linux系统配置网络详细介绍
    上一篇文章已经安装好了虚拟机和linux系统了，这次就来简单的说一下LInux系统的网络配置吧 简单介绍Linux的文件夹 bin：存放的是用户的命令 sbin：存放的是root用户的命令 etc：存放的是当前系统的环境...
    99+
    2022-06-04
    Linux网络配置的基本方法 Linux修改网络配置
  • Docker自定义网络详细介绍
    目录Docker自定义网络一.自定义网络介绍二.创建自定义网络Docker自定义网络 一.自定义网络介绍 1.介绍 常规docker容器启动,可以用–link,进行容器网络绑定,但是...
    99+
    2024-04-02
  • Docker的网络模式介绍
    这篇文章主要介绍“Docker的网络模式介绍”，在日常操作中，相信很多人在Docker的网络模式介绍问题上存在疑惑，小编查阅了各式资料，整理出简单好用的操作方法，希望对大家解答”Docker的网络模式介绍”...
    99+
    2024-04-02
  • 详细介绍GitLab的安装和配置过程
    在当今的软件开发领域，版本控制是一项非常重要的工作，而Git是这个领域中最为流行的版本控制系统之一。但是，为了更好地管理自己的项目，还需要搭建一套Git服务器来进行代码的提交和管理。其中，GitLab就是一个极好的选择。本文将详细介绍Git...
    99+
    2023-10-22
  • Docker网络配置及部署SpringCloud项目详解
    目录本次目标：一、Docker网络配置1.bridge模式(默认模式)2.host模式二、bridge模式三、host模式 四、如何创建自定义网络 1.创建自定义...
    99+
    2023-01-17
    docker网络配置 docker网络模式 docker默认的网络模式
  • docker如何配置网络
    这篇文章主要介绍了docker如何配置网络，具有一定借鉴价值，感兴趣的朋友可以参考下，希望大家阅读完这篇文章之后大有收获，下面让小编带着大家一起了解一下。Linux内核实现名称空间的创建ip netns命令可以借助ip netns命令来完成...
    99+
    2023-06-21
  • docker网络怎么配置
    本篇内容介绍了“docker网络怎么配置”的有关知识，在实际案例的操作过程中，不少人都会遇到这样的困境，接下来就让小编带领大家学习一下如何处理这些情况吧！希望大家仔细阅读，能够学有所成！Docker 配置容器的步骤是：创建一对虚拟接口在主D...
    99+
    2023-06-27
  • C++Cartographer加载配置文件过程介绍
    在node_main.cc文件中,有如下代码 std::tie(node_options, trajectory_options) = LoadOptions(FLA...
    99+
    2023-03-19
    C++ Cartographer加载配置文件 C++ Cartographer
  • phpmyadmin配置的详细介绍
    本篇内容主要讲解“phpmyadmin配置的详细介绍”，感兴趣的朋友不妨来看看。本文介绍的方法操作简单快捷，实用性强。下面就让小编来带大家学习“phpmyadmin配置的详细介绍”吧!　　phpmyadmi...
    99+
    2024-04-02
  • AndroidStudio kotlin配置详细介绍
    AndroidStudio kotlin配置安装插件File -> Settings -> Plugins -> Browse repositories -> 搜索 kotlin gradle添加依赖Module的b...
    99+
    2023-05-31
    android kotlin roi
  • windows10重置网络设置方式介绍
    很多新手客户不知道在windows10电脑中怎样进行重置网络设置，这时候客户能够点击电脑的网络图标，随后点击网络和lnternet选项，接着在通知栏找到网络重置选项哦，点击马上重设就可以啦，要是没有找到网络图标，就可以直接在输入框内搜索网络...
    99+
    2023-07-13
  • Docker 镜像导入导出过程介绍
    docker save 说明:将指定镜像保存成 tar 归档文件,以tar和tar.gz结尾都行。 语法： docker save [OPTIONS] IMAGE [IMAGE......
    99+
    2024-04-02
  • linux网络编程socket的介绍
    这篇文章主要讲解了“linux网络编程socket的介绍”，文中的讲解内容简单清晰，易于学习与理解，下面请大家跟着小编的思路慢慢深入，一起来研究和学习“linux网络编程socket的介绍”吧！一.概念介绍网络程序分为服务端程序和客户端程序...
    99+
    2023-06-13
  • Docker网络模式详解
    目录 Docker网络模式 一、Host模式 二、container模式 三、none模式 四、bridge模式 五、Overlay模式 Docker网络模式         安装Docker时会自动创建3个网络，可以使用docker ...
    99+
    2023-10-19
    docker 容器 运维 学习 网络
  • Java网络编程 - 网络编程介绍 - 网络通信三要素
    文章目录 网络编程网络编程介绍网络通信三要素要素一: IP地址IP地址基本介绍IP地址的操作类 要素二: 端口号要素三: 协议TCP协议UDP协议 网络编程 网络...
    99+
    2023-09-07
    网络 java 网络协议
  • Docker网络模型使用详解（2）Docker网络模式
    安装Docker时会自动创建3个网络，可以使用docker network ls命令列出这些网络。 [root@localhost ~]# docker network ls NETWORK ID     NAME          ...
    99+
    2023-09-08
    docker 容器 linux 运维
  • SpringCloudFeign配置应用详细介绍
    目录前言1、Feign简介2、Feign配置应用前言 服务消费者调用服务提供者的时候使用RestTemplate技术 存在不便之处： 拼接urlrestTmplate.getFor...
    99+
    2024-04-02
  • Linux启动过程详细介绍
    Linux启动过程详细介绍 启动第一步－－加载BIOS 当你打开计算机电源，计算机会首先加载BIOS信息，BIOS信息是如此的重要，以至于计算机必须在最开始就找到它。这是因为BIOS中包含了CPU的相关...
    99+
    2022-06-04
    详细介绍 过程 Linux
  • Docker 网络模式及配置方式
    一、Docker网络模式 docker run 创建 Docker 容器时，可以用 –net 选项指定容器的网络模式，Docker 有以下 4 种网络模式： host 模式，使用 –...
    99+
    2024-04-02
软考高级职称资格查询
热门wiki
近期文章
推荐阅读
热门问答
热门标签
编程网，编程工程师的家园，是目前国内优秀的开源技术社区之一，形成了由开源软件库、代码分享、资讯、协作翻译、讨论区和博客等几大频道内容，为IT开发者提供了一个发现、使用、并交流开源技术的平台。

  • 官方手机版

  • 微信公众号

  • 商务合作