docker网络的配置

最新推荐文章于 2024-07-25 08:59:53 发布

JTLuo.

最新推荐文章于 2024-07-25 08:59:53 发布

阅读量472

点赞数

分类专栏： Linux 笔记文章标签： docker

本文链接：https://blog.csdn.net/weixin_58130165/article/details/121734197

版权

Linux 同时被 2 个专栏收录

81 篇文章 0 订阅

订阅专栏

笔记

78 篇文章 1 订阅

订阅专栏

docker网络的配置

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

ip netns命令

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

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

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

[root@localhost ~]# ip netns help (属于Linux内核的命令，所以不加 "--"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

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

[root@localhost ~]# ip netns list # 列出
[root@localhost ~]#

创建Network Namespace

通过命令创建一个名为ns0的命名空间：

[root@localhost ~]# ip netns add ns0 # 创建ns0的命名空间
[root@localhost ~]# ip netns list # 列出
ns0

新创建的 Network Namespace 会出现在/var/run/netns/目录下。如果相同名字的 namespace 已经存在，命令会报Cannot create namespace file “/var/run/netns/ns0”: File exists的错误。

[root@localhost ~]# ls /var/run/netns
ns0
[root@localhost ~]# ip netns add ns0
Cannot create namespace file "/var/run/netns/ns0": File exists

# 手动创建在/var/run/netns下也是不认可的
[root@localhost ~]# touch /var/run/netns/ns1
[root@localhost ~]# ip netns list
Error: Peer netns reference is invalid. # 报错
Error: Peer netns reference is invalid.
ns1
ns0

# 删除
[root@localhost ~]# ip netns del ns1
[root@localhost ~]# ip netns list # 再次查看无报错
ns0

对于每个 Network Namespace 来说，它会有自己独立的网卡、路由表、ARP 表、iptables 等和网络相关的资源。

操作Network Namespace

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

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

[root@localhost ~]# 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@localhost ~]# ip netns exec ns0 ping 127.0.0.1
connect: Network is unreachable # 连接：网络不可达

通过下面的命令启用lo回环网卡：

[root@localhost ~]# ip netns exec ns0 ip link set lo up
[root@localhost ~]# 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.042 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.053 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@localhost ~]# 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:e0:e7:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.101.110/24 brd 192.168.101.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::a481:4471:9402:58ac/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:0b:d6:7b 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:0b:d6:7b 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 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

       
[root@localhost ~]# ip link add type veth # 创建
[root@localhost ~]# ip a # 查看
[root@localhost ~]# 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:e0:e7:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.101.110/24 brd 192.168.101.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::a481:4471:9402:58ac/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:0b:d6:7b 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:0b:d6:7b 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 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
6: veth0@veth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0a:74:26:92:7b:18 brd ff:ff:ff:ff:ff:ff
7: veth1@veth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 6a:e1:55:50:ac:5f brd ff:ff:ff:ff:ff:ff

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

实现Network Namespace间通信

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

[root@localhost ~]# ip netns list
ns0
[root@localhost ~]# ip netns add ns1
[root@localhost ~]# ip netns list
ns1
ns0

然后我们将veth0加入到ns0，将veth1加入到ns1

[root@localhost ~]# ip link set veth0 netns ns0
[root@localhost ~]# ip link set veth1 netns ns1

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

[root@localhost ~]# ip netns exec ns0 ip link set veth0 up
[root@localhost ~]# ip netns exec ns0 ip addr add 192.168.2.1/24 dev veth0

[root@localhost ~]# ip netns exec ns1 ip link set veth1 up
[root@localhost ~]# ip netns exec ns1  ip addr add 192.168.2.2/24 dev veth1

查看这对veth pair的状态

[root@localhost ~]# ip netns exec ns0 ip a
[root@localhost ~]# ip netns exec ns0 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
6: veth0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0a:74:26:92:7b:18 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::874:26ff:fe92:7b18/64 scope link 
       valid_lft forever preferred_lft forever

       
       
[root@localhost ~]#  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
7: veth1@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6a:e1:55:50:ac:5f 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::68e1:55ff:fe50:ac5f/64 scope link 
       valid_lft forever preferred_lft forever

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

[root@localhost ~]# 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.041 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.036 ms

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

veth设备重命名

重命名ns0中的veth0

[root@localhost ~]# ip netns exec ns0 ip link set veth0 down # 关闭veth0
[root@localhost ~]# ip netns exec ns0 ip link set dev veth0 name eth0 # 重命名veth0为eth0
[root@localhost ~]# ip netns exec ns0 ip link set eth0 up # 启用eth0
[root@localhost ~]# ip netns exec ns0 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
6: eth0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000   重命名成功##
    link/ether 0a:74:26:92:7b:18 brd ff:ff:ff:ff:ff:ff link-netns ns1
    inet 192.168.2.1/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::874:26ff:fe92:7b18/64 scope link 
       valid_lft forever preferred_lft forever

重命名ns1中的veth0

[root@localhost ~]# ip netns exec ns1 ip link set veth1 down #关闭veth1
[root@localhost ~]# ip netns exec ns1 ip link  set dev veth1 name eth0 # 重命名veth1为eth0
[root@localhost ~]# ip netns exec ns1 ip link set eth0 up # 启用eth0
[root@localhost ~]# 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
7: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6a:e1:55:50:ac:5f 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
    inet6 fe80::68e1:55ff:fe50:ac5f/64 scope link 
       valid_lft forever preferred_lft forever

四种网络模式配置

bridge模式配置

[root@localhost ~]# docker pull busybox
[root@localhost ~]# 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
8: eth0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0
       valid_lft forever preferred_lft forever

/ # exit

[root@localhost ~]# 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
10: eth0@if11: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0
       valid_lft forever preferred_lft forever

/ # exit

在创建容器时添加–network bridge与不加–network选项效果是一致的默认的模式

none模式

[root@localhost ~]# 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@localhost ~]# 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
12: eth0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0
       valid_lft forever preferred_lft forever
/ # 

# 重新打开一个终端使用container模式 与第一个容器相比较
[root@localhost ~]# 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
12: eth0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.2/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 QAQ
/ # ls
QAQ   bin   dev   etc   home  proc  root  sys   tmp   usr   var

# b4上查看
/ # ls
bin   dev   etc   home  proc  root  sys   tmp   usr   var

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

# 在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@localhost ~]# 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:e0:e7:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.101.110/24 brd 192.168.101.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::a481:4471:9402:58ac/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:0b:d6:7b 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:0b:d6:7b brd ff:ff:ff:ff:ff:ff
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue 
    link/ether 02:42:97:2a:95:42 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:97ff:fe2a:9542/64 scope link 
       valid_lft forever preferred_lft forever

       
[root@localhost ~]# 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:e0:e7:fa brd ff:ff:ff:ff:ff:ff
    inet 192.168.101.110/24 brd 192.168.101.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::a481:4471:9402:58ac/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:0b:d6:7b 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:0b:d6:7b 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 172.17.0.1/16 brd 172.17.255.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

  
# 此时我们在这个容器中启动一个站点，我们就可以直接用宿主机的IP直接在浏览器中访问这个容器中的站点了   
# 容器部署一个网站
/ # mkdir www
/ # echo "ccc" > www/index.html
/ # httpd -h www/

# 宿主机访问
[root@localhost ~]# curl 192.168.101.110
ccc

启动容器的时候使用host模式，那么这个容器将不会获得一个独立的Network Namespace，而是和宿主机共用一个Network Namespace。容器将不会虚拟出自己的网卡，配置自己的IP等，而是使用宿主机的IP和端口。但是，容器的其他方面，如文件系统、进程列表等还是和宿主机隔离的。

容器的常用操作

查看容器的主机名

[root@localhost ~]# docker run -it --name b6 --rm busybox
/ # hostname
730a6c4af380

在容器启动时注入主机名

[root@localhost ~]# docker run -it --name b6 --hostname jtluo busybox
/ # hostname
jtluo
/ # 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      jtluo     # 注入主机名时会自动创建主机名到IP的映射关系
/ # cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 114.114.114.114   # DNS也会自动配置为宿主机的DNS
nameserver 8.8.8.8
/ # ping baidu.com
PING baidu.com (220.181.38.251): 56 data bytes
64 bytes from 220.181.38.251: seq=0 ttl=127 time=30.270 ms
64 bytes from 220.181.38.251: seq=1 ttl=127 time=30.020 ms
/ # exit

手动指定容器要使用的DNS

[root@localhost ~]# docker run -it --rm  --name b6 --dns 8.8.8.8 --hostname jtluo busybox
/ # cat /etc/resolv.conf 
nameserver 8.8.8.8

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

[root@localhost ~]# docker run -it --name b6 --rm --hostname jtluo --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.2      jtluo

端口映射

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

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

-p选项的使用格式：

-p
- 将指定的容器端口映射至主机所有地址的一个动态端口

动态端口指的是随机端口，具体的映射结果可使用docker port命令查看。

# 将容器内nginx的80端口映射到宿主机的随机端口
[root@localhost ~]# docker run -d --name web --rm -p 80 luojiatian1904/nginx:v2
2c250e5ddfd1e82622366eba568032f6833b1dc33f77c85a8a78cbf0582d2c33
[root@localhost ~]# docker port web
80/tcp -> 0.0.0.0:49153
80/tcp -> :::49153

由此可见，容器的80端口被暴露到了宿主机的49153端口上，此时我们在宿主机上访问一下这个端口看是否能访问到容器内的站点

[root@localhost ~]# curl 192.168.101.110: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>

iptables防火墙规则将随容器的创建自动生成，随容器的暂停 / 删除自动删除规则。

-p :
- 将容器端口映射至指定的主机端口

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

[root@localhost ~]# docker run -itd --name web --rm -p 8080:80 luojiatian1904/nginx:v2
f58d3e69576a16fb9fa0682227d906871389bcae56d1b4d2f207d2a12aba0c4a
[root@localhost ~]# docker port web
80/tcp -> 0.0.0.0:8080
80/tcp -> :::8080
#宿主机访问
[root@localhost ~]# curl 192.168.101.110:8080
<!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>

-p ::
- 将指定的容器端口映射至主机指定的动态端口

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

[root@localhost ~]# docker run -itd --name web --rm -p 192.168.101.110::80 luojiatian1904/nginx:v2
7e4b2afada596ccad8f322d3bf7587f3a57d4f307c6c3347e95a958f2985d6a3
[root@localhost ~]# docker port web
80/tcp -> 192.168.101.110:49153

# 宿主机访问
[root@localhost ~]# curl 192.168.101.110: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>

-p ::
- 将指定的容器端口映射至主机指定的端口

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

[root@localhost ~]# docker run -itd --name web --rm -p 192.168.101.110:8080:80 luojiatian1904/nginx:v2
ee1efcc661c54377c155b929857b49a76652023a9e1b28314ef66b6765bc3ea6
[root@localhost ~]# docker port web
80/tcp -> 192.168.101.110:8080

# 宿主机访问
[root@localhost ~]# curl 192.168.101.110:8080
<!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>

-P(大写)将所有容器内暴露的端口发布到宿主机的随机端口

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

官方文档相关配置

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

[root@localhost ~]# cat /etc/docker/daemon.json 
{
  "registry-mirrors": ["https://wn5c7d7w.mirror.aliyuncs.com"],
  "bip": "192.168.2.1/24" # 改变宿主机的docker0网卡IP
}

[root@localhost ~]# systemctl restart docker

[root@localhost ~]# ip a
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

docker0 ip未改变之前默认是172.17.0.1/16，核心选项为bip，即bridge ip之意，用于指定docker0桥自身的IP地址；其它选项可通过此地址计算得出。

创建一个容器进去查看IP

[root@localhost ~]# docker run -itd --name web --rm luojiatian1904/nginx:v2
ee49d98c3d42a379de6f9b2f582b918032cfff812591180d1124afde4a6ec1d8
[root@localhost ~]# docker exec -it web /bin/bash
[root@ee49d98c3d42 /]# 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
28: eth0@if29: <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

docker创建自定义桥

创建一个额外的自定义桥，区别于docker0

[root@localhost ~]# docker network create -d bridge --subnet "172.17.1.0/24" --gateway "172.17.1.1" br0
67d3eef263e5fdc90660d9b153baf1c00bc2e6478de21bd140748caa5f0d7646
[root@localhost ~]# docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
67d3eef263e5   br0       bridge    local
3b28bbcc4185   bridge    bridge    local
271fa961ae4d   host      host      local
53199e28e408   none      null      local

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

[root@localhost ~]# docker run -itd --name web --network br0 --rm luojiatian1904/nginx:v2
aec728f703567b36016cf09cde1ffd1036673d7c2d961cae0b81cd09721d5cb9
[root@localhost ~]# 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@localhost ~]# docker run -itd --name web02 --rm luojiatian1904/nginx:v2
4ee412be6d20b96a18f0b6fc0062beefc2192d906b212134b362ec41be5144ff
[root@localhost ~]# 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@localhost ~]# docker run -itd --name web --network br0 --rm luojiatian1904/nginx:v2
aec728f703567b36016cf09cde1ffd1036673d7c2d961cae0b81cd09721d5cb9
[root@localhost ~]# 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@localhost ~]# docker run -itd --name web02 --rm luojiatian1904/nginx:v2
4ee412be6d20b96a18f0b6fc0062beefc2192d906b212134b362ec41be5144ff
[root@localhost ~]# 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@localhost ~]# 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@localhost ~]# 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


[root@localhost ~]# docker network connect  br0 aec728f70356(web容器ID)

# 查看web02
[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
64 bytes from 172.17.1.2: icmp_seq=2 ttl=64 time=0.090 ms