Docker之容器网络配置
Linux内核实现名称空间的创建
ip netns命令
可以借助ip netns命令来完成对 Network Namespace 的各种操作。ip netns命令来自于iproute安装包，一般系统会默认安装，如果没有的话，请自行安装。
注意：ip netns命令修改网络配置时需要 sudo 权限。
可以通过ip netns命令完成对Network Namespace 的相关操作，可以通过ip netns help查看命令帮助信息：
[root@docker ~]# yum -y install iproute
[root@docker ~]# 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
默认情况下，Linux系统中是没有任何 Network Namespace的，所以ip netns list命令不会返回任何信息。
创建Network Namespace
通过命令创建一个名为xym的命名空间：
[root@docker ~]# ip netns list
[root@docker ~]# ip netns add xym
[root@docker ~]# ip netns list
xym
新创建的 Network Namespace 会出现在/var/run/netns/目录下。如果相同名字的 namespace 已经存在，命令会报Cannot create namespace file “/var/run/netns/xym”: File exists的错误。
[root@docker ~]# ls /var/run/netns/
xym
[root@docker ~]# ip netns add xym
Cannot create namespace file "/var/run/netns/xym": File exists
对于每个 Network Namespace 来说，它会有自己独立的网卡、路由表、ARP 表、iptables 等和网络相关的资源。
操作Network Namespace
ip命令提供了ip netns exec子命令可以在对应的 Network Namespace 中执行命令。
查看新创建 Network Namespace 的网卡信息
[root@docker ~]# ip netns exec xym 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@docker ~]# ip netns exec xym ping 127.0.0.1
connect: Network is unreachable
通过下面的命令启用lo回环网卡：
[root@docker ~]# ip netns exec xym ip link set lo up
[root@docker ~]# ip netns exec xym 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.046 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.022 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.027 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 连接起来。
[root@docker ~]# 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:d1:aa:86 brd ff:ff:ff:ff:ff:ff
inet 192.168.200.150/24 brd 192.168.200.255 scope global dynamic noprefixroute ens33
valid_lft 1258sec preferred_lft 1258sec
inet6 fe80::3f7:eb08:5d5b:98f5/64 scope link noprefixroute
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:63:35:ef:ca 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@docker ~]# ip link add type veth
[root@docker ~]# 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:d1:aa:86 brd ff:ff:ff:ff:ff:ff
inet 192.168.200.150/24 brd 192.168.200.255 scope global dynamic noprefixroute ens33
valid_lft 1237sec preferred_lft 1237sec
inet6 fe80::3f7:eb08:5d5b:98f5/64 scope link noprefixroute
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:63:35:ef:ca 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
4: veth0@veth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 9a:3c:a3:f8:7c:b5 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 1a:58:1d:76:26:1c brd ff:ff:ff:ff:ff:ff
可以看到，此时系统中新增了一对veth pair，将veth0和veth1两个虚拟网卡连接了起来，此时这对 veth pair 处于”未启用“状态。
实现Network Namespace间通信
下面我们利用veth pair实现两个不同的 Network Namespace 之间的通信。刚才我们已经创建了一个名为xym Network Namespace，下面再创建一个信息Network Namespace，命名为linlu
[root@docker ~]# ip netns list
linlu
xym
[root@docker ~]# ip netns exec xym 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
[root@docker ~]# ip netns exec linlu 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
然后我们将veth0加入到xym，将veth1加入到linlu
[root@docker ~]# ip link set veth0 netns xym
[root@docker ~]# ip netns exec xym 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> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 9a:3c:a3:f8:7c:b5 brd ff:ff:ff:ff:ff:ff link-netnsid 0
[root@docker ~]# ip link set veth1 netns linlu
[root@docker ~]# ip netns exec linlu 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> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 1a:58:1d:76:26:1c brd ff:ff:ff:ff:ff:ff link-netns xym
然后我们分别为这对veth pair配置上ip地址，并启用它们
[root@docker ~]# ip netns exec xym ip link set veth0 up
[root@docker ~]# ip netns exec xym ip addr add 192.168.200.180/24 dev veth0
[root@docker ~]# ip netns exec xym 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: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state LOWERLAYERDOWN group default qlen 1000
link/ether 9a:3c:a3:f8:7c:b5 brd ff:ff:ff:ff:ff:ff link-netns linlu
inet 192.168.200.180/24 scope global veth0
valid_lft forever preferred_lft forever
[root@docker ~]# ip netns exec linlu ip link set veth1 up
[root@docker ~]# ip netns exec linlu ip addr add 192.168.200.190/24 dev veth1
[root@docker ~]# ip netns exec linlu 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 1a:58:1d:76:26:1c brd ff:ff:ff:ff:ff:ff link-netns xym
inet 192.168.200.190/24 scope global veth1
valid_lft forever preferred_lft forever
inet6 fe80::1858:1dff:fe76:261c/64 scope link
valid_lft forever preferred_lft forever
从上面可以看出，我们已经成功启用了这个veth pair，并为每个veth设备分配了对应的ip地址。我们尝试在ns1中访问ns0中的ip地址：
[root@docker ~]# ip netns exec xym ping 192.168.200.190
PING 192.168.200.190 (192.168.200.190) 56(84) bytes of data.
64 bytes from 192.168.200.190: icmp_seq=1 ttl=64 time=0.038 ms
64 bytes from 192.168.200.190: icmp_seq=2 ttl=64 time=0.025 ms
可以看到，veth pair成功实现了两个不同Network Namespace之间的网络交互。
veth设备重命名
[root@docker ~]# ip netns exec xym ip link set veth0 down
[root@docker ~]# ip netns exec xym ip link set dev veth0 name eth0[root@docker ~]# ip netns exec xym ip link set eth0 up
[root@docker ~]# ip netns exec xym 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: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 9a:3c:a3:f8:7c:b5 brd ff:ff:ff:ff:ff:ff link-netns linlu
inet 192.168.200.180/24 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::983c:a3ff:fef8:7cb5/64 scope link
valid_lft forever preferred_lft forever
四种网络模式配置
bridge模式配置
[root@docker ~]# docker run -it --name nginx --rm linlusama/centos-nginx:v1.20.1 /bin/sh
sh-4.4# 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
6: eth0@if7: <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
sh-4.4# exit
exit
[root@docker ~]# docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
# 在创建容器时添加--network bridge与不加--network选项效果是一致的
[root@docker ~]# docker run -it --name nginx --rm --network bridge linlusama/centos-nginx:v1.20.1 /bin/sh
sh-4.4# 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
8: eth0@if9: <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
none模式配置
[root@docker ~]# docker run -it --name nginx --rm --network none linlusama/centos-nginx:v1.20.1 /bin/sh
sh-4.4# 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
container模式配置
启动第一个容器
[root@docker ~]# docker run -it --name nginx1 --rm linlusama/centos-nginx:v1.20.1 /bin/sh
sh-4.4# 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
10: eth0@if11: <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@docker ~]# docker run -it --name nginx2 --rm --network container:nginx1 linlusama/centos-nginx:v1.20.1 /bin/sh
sh-4.4# 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
10: eth0@if11: <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
此时我们在b1容器上创建一个目录
sh-4.4# mkdir /tmp/xym
sh-4.4# ls /tmp/
ks-script-4luisyla ks-script-o23i7rc2 ks-script-x6ei4wuu xym
//nginx2看没有
sh-4.4# ls /tmp/
ks-script-4luisyla ks-script-o23i7rc2 ks-script-x6ei4wuu
到b2容器上检查/tmp目录会发现并没有这个目录，因为文件系统是处于隔离状态，仅仅是共享了网络而已。
在b2容器上部署一个站点
sh-4.4# mkdir -p /var/www/html
sh-4.4# echo "重生之我是徐猛他爹" > /var/www/html/index.html
sh-4.4# /bin/httpd -f -h /var/www/html/index.html
在b1容器上用本地地址去访问此站点
sh-4.4# wget -qO - 127.0.0.1
重生之我是徐猛他爹
由此可见，container模式下的容器间关系就相当于一台主机上的两个不同进程
host模式配置
启动容器时直接指明模式为host
[root@docker ~]# docker run -it --name nginx --rm --network host linlusama/centos-nginx:v1.20.1 /bin/sh
sh-4.4# 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:d1:aa:86 brd ff:ff:ff:ff:ff:ff
inet 192.168.200.150/24 brd 192.168.200.255 scope global dynamic noprefixroute ens33
valid_lft 1158sec preferred_lft 1158sec
inet6 fe80::3f7:eb08:5d5b:98f5/64 scope link noprefixroute
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:63:35:ef:ca 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:63ff:fe35:efca/64 scope link
valid_lft forever preferred_lft forever
此时如果我们在这个容器中启动一个http站点，我们就可以直接用宿主机的IP直接在浏览器中访问这个容器中的站点了。
sh-4.4# echo "woshinidie" > /usr/local/nginx/html/index.html
sh-4.4# /usr/local/nginx/sbin/nginx
sh-4.4# ss -antl
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 25 0.0.0.0:514 0.0.0.0:*
LISTEN 0 128 0.0.0.0:80 0.0.0.0:*
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 25 [::]:514 [::]:*
LISTEN 0 128 [::]:22 [::]:*
容器的常用操作
查看容器的主机名
[root@docker ~]# docker run -it --name nginx -p 80:80 linlusama/centos-nginx:v1.20.2 /bin/bash
[root@b16c5957d542 /]# hostname
b16c5957d542
在容器启动时注入主机名
[root@docker ~]# docker run -it --rm --hostname node1 centos /bin/bash
[root@node1 /]# 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 node1
[root@node1 /]# cat /etc/resolv.conf //将网关设置成宿主机的网关
# Generated by NetworkManager
search localdomain
nameserver 192.168.200.2
[root@node1 /]# ping www.baidu.com
PING www.a.shifen.com (36.152.44.95) 56(84) bytes of data.
64 bytes from localhost (36.152.44.95): icmp_seq=1 ttl=127 time=44.4 ms
64 bytes from localhost (36.152.44.95): icmp_seq=2 ttl=127 time=43.5 ms
手动指定容器要使用的DNS
[root@docker ~]# docker run -it --rm --hostname node1 --dns 8.8.8.8 centos /bin/bash
[root@node1 /]# cat /etc/resolv.conf
search localdomain
nameserver 8.8.8.8
手动往/etc/hosts文件中注入主机名到IP地址的映射
[root@docker ~]# docker run -it --rm --hostname node1 --add-host node2:192.168.200.145 centos /bin/bash
[root@node1 /]# 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
192.168.200.145 node2
172.17.0.3 node1
开放容器端口
执行docker run的时候有个-p选项，可以将容器中的应用端口映射到宿主机中，从而实现让外部主机可以通过访问宿主机的某端口来访问容器内应用的目的。
-p选项能够使用多次，其所能够暴露的端口必须是容器确实在监听的端口。
-p选项的使用格式：
- -p <containerPort>
- 将指定的容器端口映射至主机所有地址的一个动态端口
- -p <hostPort>:<containerPort>
- 将容器端口<containerPort>映射至指定的主机端口<hostPort>
- -p <ip>::<containerPort>
- 将指定的容器端口<containerPort>映射至主机指定<ip>的动态端口
- -p <ip>:<hostPort>:<containerPort>
- 将指定的容器端口<containerPort>映射至主机指定<ip>的端口<hostPort>
动态端口指的是随机端口，具体的映射结果可使用docker port命令查看。
[root@docker ~]# docker run -it --rm --name nginx -p 80 linlusama/centos-nginx:v1.20.2 /bin/bash
以上命令执行后会一直占用着前端，我们新开一个终端连接来看一下容器的80端口被映射到了宿主机的什么端口上
[root@docker ~]# docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
286002a8316b linlusama/centos-nginx:v1.20.2 "/bin/bash" About a minute ago Up About a minute 0.0.0.0:49153->80/tcp, :::49153->80/tcp nginx
root@docker ~]# ss -antl
State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess
LISTEN 0 128 0.0.0.0:49153 0.0.0.0:*
LISTEN 0 25 0.0.0.0:514 0.0.0.0:*
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 128 [::]:49153 [::]:*
LISTEN 0 25 [::]:514 [::]:*
LISTEN 0 128 [::]:22 [::]:*
由此可见，容器的80端口被暴露到了宿主机的49153端口上，此时我们在宿主机上访问一下这个端口看是否能访问到容器内的站点
[root@docker ~]# curl http://127.0.0.1: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防火墙规则将随容器的创建自动生成，随容器的删除自动删除规则。
将容器端口映射到指定IP的随机端口
[root@docker ~]# docker run -itd --rm --name nginx -p 192.168.200.150::80 linlusama/centos-nginx:v1.20.1
e1d06b64f07ddf8625c3b473992a217bae3fb6f0e59ca5eceeb1a5e4f7537f6b
在另一个终端上查看端口映射情况
[root@docker ~]# docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e1d06b64f07d linlusama/centos-nginx:v1.20.1 "/usr/local/nginx/sb…" 3 seconds ago Up 2 seconds 192.168.200.150:49153->80/tcp nginx
[root@docker ~]# curl 192.168.200.150:49153
我是徐猛他爹
将容器端口映射到宿主机的指定端口
[root@docker ~]# docker run -itd --rm --name nginx -p 8080:80 linlusama/centos-nginx:v1.20.1
87ba6e9db605786c198ce8cfc2772ec715465b8d5e455eed7d0cc6aad4597e2e
在另一个终端上查看端口映射情况
[root@docker ~]# docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
87ba6e9db605 linlusama/centos-nginx:v1.20.1 "/usr/local/nginx/sb…" 3 seconds ago Up 2 seconds 0.0.0.0:8080->80/tcp, :::8080->80/tcp nginx
[root@docker ~]# ss -antl
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 25 0.0.0.0:514 0.0.0.0:*
LISTEN 0 128 0.0.0.0:8080 0.0.0.0:*
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 25 [::]:514 [::]:*
LISTEN 0 128 [::]:8080 [::]:*
LISTEN 0 128 [::]:22 [::]:*
[root@docker ~]# curl 192.168.200.150:8080
我是徐猛他爹
自定义docker0桥的网络属性信息
自定义docker0桥的网络属性信息需要修改/etc/docker/daemon.json配置文件
[root@docker ~]# cat /etc/docker/daemon.json
{
"registry-mirrors": ["https://6yrl18rf.mirror.aliyuncs.com"],
"bip": "192.168.66.88/24"
}
[root@docker ~]# systemctl restart docker
[root@docker ~]# 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:d1:aa:86 brd ff:ff:ff:ff:ff:ff
inet 192.168.200.150/24 brd 192.168.200.255 scope global dynamic noprefixroute ens33
valid_lft 1464sec preferred_lft 1464sec
inet6 fe80::3f7:eb08:5d5b:98f5/64 scope link noprefixroute
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:63:35:ef:ca brd ff:ff:ff:ff:ff:ff
inet 192.168.66.88/24 brd 192.168.66.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:63ff:fe35:efca/64 scope link
valid_lft forever preferred_lft forever
核心选项为bip，即bridge ip之意，用于指定docker0桥自身的IP地址；其它选项可通过此地址计算得出。
docker远程连接
dockerd守护进程的C/S，其默认仅监听Unix Socket格式的地址(/var/run/docker.sock)，如果要使用TCP套接字，则需要修改/etc/docker/daemon.json配置文件，添加如下内容，然后重启docker服务：
"hosts": ["tcp://0.0.0.0:2375", "unix:///var/run/docker.sock"]
在客户端上向dockerd直接传递“-H|–host”选项指定要控制哪台主机上的docker容器
docker -H 192.168.10.145:2375 ps
docker创建自定义桥
创建一个额外的自定义桥，区别于docker0
[root@docker ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
46a740510c53 bridge bridge local
e60478a9ce12 host host local
b1eca0cb44c6 none null local
[root@docker ~]# docker network create -d bridge --subnet "192.168.88.0/24" --gateway "192.168.88.1" br0
d972ef8d61498e25b29c9bb0b0978c9c9505e35d84158d308aa7790cc08942e5
[root@docker ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
d972ef8d6149 br0 bridge local
46a740510c53 bridge bridge local
e60478a9ce12 host host local
b1eca0cb44c6 none null local
使用新创建的自定义桥来创建容器：
[root@docker ~]# docker run -it --rm --name nginx --network br0 centos
[root@62554f569846 /]# 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:c0:a8:58:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.88.2/24 brd 192.168.88.255 scope global eth0
valid_lft forever preferred_lft forever
再创建一个容器，使用默认的bridge桥：
[root@docker ~]# docker run -it --rm --name nginx1 --network bridge centos
[root@b65b63b12508 /]# 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:42:01 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.66.1/24 brd 192.168.66.255 scope global eth0
valid_lft forever preferred_lft forever
试想一下，此时的b2与b1能否互相通信？如果不能该如何实现通信？
我们可以把桥连接过去，br0是我们上传创建的，把默认桥连接到刚刚创建的桥
[root@docker ~]# docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0d42fbacaf65 centos "/bin/bash" 24 seconds ago Up 23 seconds nginx1
4e9457637bbd centos "/bin/bash" About a minute ago Up About a minute nginx
[root@docker ~]# docker network connect br0 0d42fbacaf65
再到nginx1容器中去ping
[root@0d42fbacaf65 /]# 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
37: eth0@if38: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:c0:a8:42:01 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.66.1/24 brd 192.168.66.255 scope global eth0
valid_lft forever preferred_lft forever
39: eth1@if40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:c0:a8:58:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 192.168.88.3/24 brd 192.168.88.255 scope global eth1
valid_lft forever preferred_lft forever
[root@0d42fbacaf65 /]# ping 192.168.88.2
PING 192.168.88.2 (192.168.88.2) 56(84) bytes of data.
64 bytes from 192.168.88.2: icmp_seq=1 ttl=64 time=0.103 ms
64 bytes from 192.168.88.2: icmp_seq=2 ttl=64 time=0.050 ms
64 bytes from 192.168.88.2: icmp_seq=3 ttl=64 time=0.073 ms
64 bytes from 192.168.88.2: icmp_seq=4 ttl=64 time=0.049 ms
64 bytes from 192.168.88.2: icmp_seq=5 ttl=64 time=0.051 ms
^C
--- 192.168.88.2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4134ms
rtt min/avg/max/mdev = 0.049/0.065/0.103/0.021 ms
扫一扫
827
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
