docker容器网络配置

暖春忽见

已于 2022-08-10 14:15:29 修改

阅读量616

点赞数

分类专栏：奋斗文章标签： docker 网络 linux

于 2022-08-10 13:25:51 首次发布

本文链接：https://blog.csdn.net/nuanchunhujian/article/details/126264661

版权

奋斗专栏收录该内容

19 篇文章 0 订阅

订阅专栏

docker容器网络配置

文章目录

docker容器网络配置
@[toc]
ip netns命令
创建Network Namespace
操作Network Namespace
创建veth pair
实现Network Namespace间通信
veth设备重命名

四种网络模式配置
bridge模式配置
none模式配置
container模式配置
host模式配置

容器的常用操作
查看容器的主机名
在容器启动时注入主机名
手动指定容器要使用的DNS
手动往/etc/hosts文件中注入主机名到IP地址的映射

ip netns命令

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

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

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

#查看IP netns 帮助
[root@hostlocal ~]# 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@hostlocal ~]#

默认情况下，Linux系统中是没有任何 Network Namespace的，所以ip netns list命令不会返回任何信息。

创建Network Namespace

#通过命令创建一个名为ns0的命名空间：新创建的 Network Namespace 会出现在/var/run/netns/目录下。如果相同名字的 namespace 已经存在，命令会报Cannot create namespace file "/var/run/netns/ns0": File exists的错误。
[root@hostlocal ~]# ip netns add ns0
[root@hostlocal ~]# ip netns list
ns0
[root@hostlocal ~]# 
[root@hostlocal ~]# ls /var/run/netns/
ns0
[root@hostlocal ~]# ip netns add ns0
Cannot create namespace file "/var/run/netns/ns0": File exists
[root@hostlocal ~]#

操作Network Namespace

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

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

[root@hostlocal ~]# 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
[root@hostlocal ~]#

可以看到，新创建的Network Namespace中会默认创建一个lo回环网卡，此时网卡处于关闭状态。此时，尝试去 ping 该lo回环网卡，会提示Network is unreachable

[root@hostlocal ~]# ip netns exec ns0 ping 127.0.0.1
connect: Network is unreachable
[root@hostlocal ~]# 
[root@hostlocal ~]# ip netns exec ns0 ip link set lo up
[root@hostlocal ~]# 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.032 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.048 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.046 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.050 ms

创建veth pair

[root@hostlocal ~]# ip link add type veth
[root@hostlocal ~]# ip a
4: veth0@veth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 5a:7f:ac:3e:38:5e brd ff:ff:ff:ff:ff:ff
5: veth1@veth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c2:cd:41:f1:55:e9 brd ff:ff:ff:ff:ff:ff
[root@hostlocal ~]#

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

实现Network Namespace间通信

下面我们利用veth pair实现两个不同的 Network Namespace 之间的通信。刚才我们已经创建了一个名为ns0的 Network Namespace，下面再创建一个信息Network Namespace，命名为ns1

[root@hostlocal ~]# ip netns add ns1
[root@hostlocal ~]# ip netns list
ns1
ns0
[root@hostlocal ~]# 
#然后我们将veth0加入到ns0，将veth1加入到ns1
[root@hostlocal ~]# ip link set veth0 netns ns0
[root@hostlocal ~]# ip link set veth1 netns ns1

然后我们分别为这对veth pair配置上ip地址，并启用它们

[root@hostlocal ~]# ip netns exec ns0 ip link set veth0 up
[root@hostlocal ~]# ip netns exec ns0 ip addr add 192.168.171.1/24 dev veth0 
[root@hostlocal ~]# ip netns exec ns1 ip link set lo up
[root@hostlocal ~]# ip netns exec ns1 ip link set veth1 up
[root@hostlocal ~]# ip nstns exec ns1 ip addr add 192.168.171.2/24 dev veth1
[root@hostlocal ~]# ip netns exec ns1 ip addr add 192.168.171.2/24 dev veth1
#然后IP a查看状态
[root@hostlocal ~]# 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
4: veth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5a:7f:ac:3e:38:5e brd ff:ff:ff:ff:ff:ff link-netns ns1
    inet 192.168.171.1/24 scope global veth0
       valid_lft forever preferred_lft forever
    inet6 fe80::587f:acff:fe3e:385e/64 scope link 
       valid_lft forever preferred_lft forever
[root@hostlocal ~]# ip netns exec ns1 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
5: veth1@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c2:cd:41:f1:55:e9 brd ff:ff:ff:ff:ff:ff link-netns ns0
    inet 192.168.171.2/24 scope global veth1
       valid_lft forever preferred_lft forever
    inet6 fe80::c0cd:41ff:fef1:55e9/64 scope link 
       valid_lft forever preferred_lft forever

从上面可以看出，我们已经成功启用了这个veth pair，并为每个veth设备分配了对应的ip地址。我们尝试在ns1中访问ns0中的ip地址：

[root@hostlocal ~]# ip netns exec ns1 ping 192.168.171.1
PING 192.168.171.1 (192.168.171.1) 56(84) bytes of data.
64 bytes from 192.168.171.1: icmp_seq=1 ttl=64 time=0.053 ms
64 bytes from 192.168.171.1: icmp_seq=2 ttl=64 time=0.058 ms
64 bytes from 192.168.171.1: icmp_seq=3 ttl=64 time=0.060 ms
64 bytes from 192.168.171.1: icmp_seq=4 ttl=64 time=0.060 ms

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

veth设备重命名

[root@hostlocal ~]# ip netns exec ns0 ip a
[root@hostlocal ~]# ip netns exec ns0 ip link set veth0 down
[root@hostlocal ~]# ip netns exec ns0 ip link set dev veth0 name eth0
[root@hostlocal ~]# ip netns exec ns0 ifconfig -a
eth0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.171.1  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 5a:7f:ac:3e:38:5e  txqueuelen 1000  (Ethernet)
        RX packets 18  bytes 1412 (1.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 18  bytes 1412 (1.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 8  bytes 672 (672.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8  bytes 672 (672.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@hostlocal ~]#

四种网络模式配置

bridge模式配置

[root@hostlocal ~]# docker run -it --name t1 --rm busybox
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
5cc84ad355aa: Pull complete 
Digest: sha256:5acba83a746c7608ed544dc1533b87c737a0b0fb730301639a0179f9344b1678
Status: Downloaded newer image for busybox:latest
/ # ifconfig 
eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:02  
          inet addr:172.17.0.2  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1182 (1.1 KiB)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
# 在创建容器时添加--network bridge与不加--network选项效果是一致的
[root@hostlocal ~]# docker run -it --name t1 --network bridge --rm busybox
/ # ifconfig 
eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:02  
          inet addr:172.17.0.2  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:736 (736.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

/ #

none模式配置

[root@hostlocal ~]# docker run -it --name t1 --network none --rm busybox
/ # ifconfig -a
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

/ #

container模式配置

启动第一个容器

[root@hostlocal ~]# docker run -it --name b1 --rm busybox 
/ # ifconfig
eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:02  
          inet addr:172.17.0.2  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:806 (806.0 B)  TX bytes:0 (0.0 B)

启动第二个容器

[root@hostlocal ~]# docker run -it --name b2 --rm busybox
/ # ifconfig 
eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:02  
          inet addr:172.17.0.2  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:736 (736.0 B)  TX bytes:0 (0.0 B)

可以看到名为b2的容器IP地址是172.17.0.2，与第一个容器的IP地址不是一样的，也就是说并没有共享网络，此时如果我们将第二个容器的启动方式改变一下，就可以使名为b2的容器IP与B1容器IP一致，也即共享IP，但不共享文件系统。

[root@hostlocal ~]# docker run -it --name b2 --rm --network container:b1 busybox
/ # ifconfig
eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:02  
          inet addr:172.17.0.2  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:806 (806.0 B)  TX bytes:0 (0.0 B)

此时我们在b1容器上创建一个目录

/ # ls
bin   dev   etc   home  proc  root  sys   tmp   usr   var
/ # mkdir /tmp/data
/ # ls /tmp/
data
/ #

到b2容器上检查/tmp目录会发现并没有这个目录，因为文件系统是处于隔离状态，仅仅是共享了网络而已。

在b2容器上部署一个站点

/ # echo 'hello world' > /tmp/index.html
/ # ls /tmp/
index.html
/ # httpd -h /tmp/
/ # netstat -antl
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 :::80                   :::*                    LISTEN      
/ #

在b1容器上用本地地址去访问此站点

/ # ifconfig 
eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:02  
          inet addr:172.17.0.2  Bcast:172.17.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1086 (1.0 KiB)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

/ # wget -O - -q 127.0.0.1:80
hello world
/ #

由此可见，container模式下的容器间关系就相当于一台主机上的两个不同进程

host模式配置

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

[root@hostlocal ~]# docker run -it --name b2 --rm --network host busybox
/ # ifconfig 
docker0   Link encap:Ethernet  HWaddr 02:42:0E:4A:CC:8A  
          inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
          inet6 addr: fe80::42:eff:fe4a:cc8a/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:2066 (2.0 KiB)

ens33     Link encap:Ethernet  HWaddr 00:0C:29:22:9F:4E  
          inet addr:192.168.171.134  Bcast:192.168.171.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe22:9f4e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:252476 errors:0 dropped:0 overruns:0 frame:0
          TX packets:222072 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:171141045 (163.2 MiB)  TX bytes:30471831 (29.0 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

/ #

此时如果我们在这个容器中启动一个http站点，我们就可以直接用宿主机的IP直接在浏览器中访问这个容器中的站点了

容器的常用操作

查看容器的主机名

[root@hostlocal ~]# docker run -it --name t1 --network bridge --rm busybox
/ # hostname
373c49c965d5
/ #

在容器启动时注入主机名

[root@hostlocal ~]# docker run -it --name t1 --network bridge --hostname Tatum --rm busybox
/ # hostname 
Tatum
/ # 
/ # 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.2      Tatum  	#注入主机名时会自动创建主机名到IP的映射关系
/ # cat /etc/resolv.conf 
# Generated by NetworkManager
search localdomain
nameserver 192.168.171.2
/ # 
/ # ping www.baidu.com
PING www.baidu.com (112.80.248.75): 56 data bytes
64 bytes from 112.80.248.75: seq=0 ttl=127 time=53.192 ms
64 bytes from 112.80.248.75: seq=1 ttl=127 time=58.016 ms
64 bytes from 112.80.248.75: seq=2 ttl=127 time=109.944 ms
^C
--- www.baidu.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 53.192/73.717/109.944 ms

手动指定容器要使用的DNS

[root@hostlocal ~]# docker run -it --name t1 --network bridge --hostname tatum --dns 114.114.114.114 --rm busybox
/ # cat /etc/resolv.conf 
search localdomain
nameserver 114.114.114.114
/ # nslookup -type=a www.baidu.com
Server:         114.114.114.114
Address:        114.114.114.114:53

Non-authoritative answer:
www.baidu.com   canonical name = www.a.shifen.com
Name:   www.a.shifen.com
Address: 110.242.68.3
Name:   www.a.shifen.com
Address: 110.242.68.4

/ #

手动往/etc/hosts文件中注入主机名到IP地址的映射

[root@hostlocal ~]# docker run -it --name t1 --network bridge --hostname tatum --add-host www.a.com:1.1.1.1 --rm 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
1.1.1.1 www.a.com
172.17.0.2      tatum
/ #

Name: www.a.shifen.com
Address: 110.242.68.4

/ #


### 手动往/etc/hosts文件中注入主机名到IP地址的映射

```bash
[root@hostlocal ~]# docker run -it --name t1 --network bridge --hostname tatum --add-host www.a.com:1.1.1.1 --rm 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
1.1.1.1 www.a.com
172.17.0.2      tatum
/ #