docker容器网络配置
Linux内核实现名称空间的创建
IP netns命令
可以借助ip netns命令来完成对 Network Namespace 的各种操作。ip netns命令来自于iproute安装包，一般系统会默认安装，如果没有的话，请自行安装。
注意：ip netns命令修改网络配置时需要 sudo 权限。
可以通过ip netns命令完成对Network Namespace 的相关操作，可以通过ip netns help查看命令帮助信息：
[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
NETNSID := auto | POSITIVE-INT
默认情况下，Linux系统中是没有任何 Network Namespace的，所以ip netns list命令不会返回任何信息。
创建Network Namespace
通过命令创建一个名为sb0的命名空间：
[root@docker ~]# ip netns list //查看列表
[root@docker ~]#
[root@docker ~]# ip netns add dr0 //新建
[root@docker ~]# ip netns list
dr0
新创建的 Network Namespace 会出现在/var/run/netns/目录下。如果相同名字的 namespace 已经存在，命令会报Cannot create namespace file “/var/run/netns/sb0”: File exists的错误。
[root@docker ~]# ip netns list //列表中已存在dr0
dr0
[root@docker ~]# ls /var/run/netns/
dr0
[root@docker ~]# ip netns add dr0
Cannot create namespace file "/var/run/netns/dr0": File exists
对于每个 Network Namespace 来说，它会有自己独立的网卡、路由表、ARP 表、iptables 等和网络相关的资源。
操作Network Namespace
ip命令提供了 ip netns exec 子命令可以在对应的 Network Namespace 中执行命令。
查看新创建 Network Namespace 的网卡信息如下：
[root@docker ~]# ip netns exec dr0 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 dr0 ping 127.0.0.1
connect: 网络不可达
那么如何解决呢？
通过下面的命令启用lo回环网卡：
[root@docker ~]# ip netns exec dr0 ip link set lo up // 启动lo环回
[root@docker ~]# ip netns exec dr0 ping 127.0.0.1 //使用ping测试
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data. // 可以ping tomg
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.076 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.071 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.065 ms
--- 127.0.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 48ms
rtt min/avg/max/mdev = 0.065/0.070/0.076/0.010 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@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: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0c:29:b7:b0:df brd ff:ff:ff:ff:ff:ff
inet 192.168.58.10/24 brd 192.168.58.255 scope global noprefixroute ens160
valid_lft forever preferred_lft forever
inet6 fe80::ca43:3f86:3176:184c/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: veth0@veth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d2:6d:a1:7a:e0:4a brd ff:ff:ff:ff:ff:ff
4: veth1@veth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether c6:d4:08:89:2a:22 brd ff:ff:ff:ff:ff:ff
可以看到，此时系统中新增了一对veth pair，将veth0和veth1两个虚拟网卡连接了起来，此时这对 veth pair 处于”未启用“状态。
实现Network Namespace间通信
下面我们利用veth pair实现两个不同的 Network Namespace 之间的通信。刚才我们已经创建了一个名为ns0的 Network Namespace，下面再创建一个信息Network Namespace，命名为by2
[root@docker ~]# ip netns add by2
[root@docker ~]# ip netns list
by2
dr0
然后我们将veth0介入到dr0，将veth1加入到by2
[root@docker ~]# ip link set veth0 netns dr0
[root@docker ~]# ip link set veth1 netns by2
然后我们分别为这对veth pair配置上ip地址，并启用它们
[root@docker ~]# ip netns exec dr0 ip link set veth0 up
[root@docker ~]# ip netns exec dr0 ip addr add 192.168.50.20/24 dev veth0
[root@docker ~]# ip netns exec by2 ip link set lo up
[root@docker ~]# ip netns exec by2 ip link set veth1 up
[root@docker ~]# ip netns exec by2 ip addr add 192.168.50.30/24 dev veth1
查看这对veth pair的状态
veth 0
[root@docker ~]# ip netns exec dr0 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
3: veth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether d2:6d:a1:7a:e0:4a brd ff:ff:ff:ff:ff:ff link-netns by2
inet 192.168.50.20/24 scope global veth0
valid_lft forever preferred_lft forever
inet6 fe80::d06d:a1ff:fe7a:e04a/64 scope link
valid_lft forever preferred_lft forever
veth 1
[root@docker ~]# ip netns exec by2 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: veth1@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c6:d4:08:89:2a:22 brd ff:ff:ff:ff:ff:ff link-netns dr0
inet 192.168.50.30/24 scope global veth1
valid_lft forever preferred_lft forever
inet6 fe80::c4d4:8ff:fe89:2a22/64 scope link
valid_lft forever preferred_lft forever
从上面可以看出，我们已经成功启用了这个veth pair，并为每个veth设备分配了对应的ip地址。我们尝试在dr0中访问by2中的ip地址：
[root@docker ~]# ip netns exec dr0 ping 192.168.50.30
PING 192.168.50.30 (192.168.50.30) 56(84) bytes of data.
64 bytes from 192.168.50.30: icmp_seq=1 ttl=64 time=0.395 ms
64 bytes from 192.168.50.30: icmp_seq=2 ttl=64 time=0.127 ms
64 bytes from 192.168.50.30: icmp_seq=3 ttl=64 time=0.049 ms
--- 192.168.50.30 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 63ms
rtt min/avg/max/mdev = 0.049/0.190/0.395/0.148 ms
在by2上尝试访问dr0的ip地址
[root@docker ~]# ip netns exec by2 ping 192.168.50.20
PING 192.168.50.20 (192.168.50.20) 56(84) bytes of data.
64 bytes from 192.168.50.20: icmp_seq=1 ttl=64 time=0.086 ms
64 bytes from 192.168.50.20: icmp_seq=2 ttl=64 time=0.092 ms
64 bytes from 192.168.50.20: icmp_seq=3 ttl=64 time=0.109 ms
--- 192.168.50.20 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 67ms
rtt min/avg/max/mdev = 0.086/0.095/0.109/0.014 ms
可以看到，veth pair成功实现了两个不同Network Namespace之间的网络交互。
veth设备重命名
注意：在给veth 设备重命名之前应该先down 指定网卡
[root@docker ~]# ip netns exec dr0 ip link set veth0 down //关闭网卡
[root@docker ~]# ip netns exec dr0 ip link set dev veth0 name ens30 //指定veth 0 并修改名称
[root@docker ~]# ip netns exec dr0 ip link set ens30 up //启动修改后的veth 30 网卡
[root@docker ~]# ip netns exec dr0 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
3: ens30@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether d2:6d:a1:7a:e0:4a brd ff:ff:ff:ff:ff:ff link-netns by2
inet 192.168.50.20/24 scope global ens30
valid_lft forever preferred_lft forever
inet6 fe80::d06d:a1ff:fe7a:e04a/64 scope link
valid_lft forever preferred_lft forever
四种网络模式配置
bridge模式配置
[root@docker ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
tomcat latest 904a98253fbf 2 weeks ago 680MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
// 运行一个容器
[root@docker ~]# docker run -dit --name test1 --rm busybox
[root@docker ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0caf5e9d1775 busybox "sh" 29 seconds ago Up 20 seconds test1
[root@docker ~]# docker exec -it 0caf5e9d1775 /bin/sh
/ # 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
6: eth0@if7: <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@docker ~]# docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0caf5e9d1775 busybox "sh" 3 minutes ago Up 3 minutes test1
在创建容器时添加 --network bridge与不加 --network选项效果是一样的
使用 network bridge 模式创建一个容器
[root@docker ~]# docker run -dit --name test --network bridge busybox
0f7cfbf71a61d852c8759524dff6f582577a993d91a10bc840e9e4016703b37a
[root@docker ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0f7cfbf71a61 busybox "sh" 10 seconds ago Up 3 seconds test
[root@docker ~]# docker exec -it test /bin/sh
/ # 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
none模式
[root@docker ~]# docker run -dit --name test1 --network none busybox
17da1e6d5a2bce6a82f0c361e3af54463b3a72c0e8be0e8bcd7f9352aa7a94cb
[root@docker ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
17da1e6d5a2b busybox "sh" 6 seconds ago Up 4 seconds test1
[root@docker ~]# docker exec -it test1 /bin/sh
/ # 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
/ #
container模式配置
//创建一个名为test2容器
[root@docker ~]# docker run -dit --name test2 busybox
fc13e3c08469083f7c1c7fd0b6e5e119e40a34920dc6e33ca3a32d2cab02bb8e
[root@docker ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
fc13e3c08469 busybox "sh" 13 seconds ago Up 11 seconds test2
//进入容器查看ip
[root@docker ~]# docker exec -it test2 /bin/sh
/ # 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
// ip 为172.17.0.3
启动第二个容器
[root@docker ~]# docker run -it --name test3 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:04 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.4/16 brd 172.17.255.255 scope global eth0
valid_lft forever preferred_lft forever
可以看到名为test3的容器IP地址是172.17.0.4，与第一个容器的IP地址不是一样的，也就是说并没有共享网络，此时如果我们将第二个容器的启动方式改变一下，就可以使名为test3的容器IP与test2容器IP一致，也即共享IP，但不共享文件系统。
//在创建容器之前 先停止并删除同名容器
[root@docker ~]# docker stop test3
test3
[root@docker ~]# docker rm test3
test3
[root@docker ~]# docker run -it --name test3 --network container:test2 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: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
// 此时的test3 容器与test2的ip一致了
此时我们另起一个控制终端
在test2容器上的tmp目录创建一个data目录
[root@docker ~]# docker exec -it test2 /bin/sh
/ # cd /tmp/
/tmp # mkdir data
/tmp # ls
data
到test3容器上检查/tmp目录会发现并没有这个目录，因为文件系统是处于隔离状态，仅仅是共享了网络而已。
/ # ls /tmp/
/ #
实例
在test2 主机上设置一个站点
/tmp # echo 'hell Java!' > /tmp/index.html
/tmp # sl /tmp/
/tmp # ls /tmp/
data index.html
/ # httpd -h /tmp/
/ # netstat -anlt
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 :::80 :::* LISTEN
在test3容器上用本地地址去访问此站点
/ # wget -qO - 127.0.0.1
hell Java!
/ #
由此可见，container模式下的容器间关系就相当于一台主机上的两个不同进程
host模式配置
启动容器时直接指明模式为host
[root@docker ~]# docker run -it --name aa --rm --network host busybox /bin/sh
/ # 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: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
link/ether 00:0c:29:b7:b0:df brd ff:ff:ff:ff:ff:ff
inet 192.168.58.10/24 brd 192.168.58.255 scope global noprefixroute ens160
valid_lft forever preferred_lft forever
inet6 fe80::ca43:3f86:3176:184c/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether 02:42:92:e8:49:61 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:92ff:fee8:4961/64 scope link
valid_lft forever preferred_lft forever
此时如果我们在这个容器中启动一个http站点，我们就可以直接用宿主机的IP直接在浏览器中访问这个容器中的站点了。
在容器里面部署一个http站点，在这里来测试一下：
/ # touch /tmp/index.html
/ # echo 'test' > /tmp/index.html
/ # httpd -h /tmp/
使用宿主机ip+port(80) 访问测试
容器的常用操作
查看容器的主机名
[root@docker ~]# docker run -dit --name ja busybox /bin/sh //运行一个容器
7c230c5e540c46990de15853654dabb6e8bb7aef53897ac231d53eed22892342
[root@docker ~]# docker ps -a //查看运行状态
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7c230c5e540c busybox "/bin/sh" 4 seconds ago Up 3 seconds ja
[root@docker ~]# docker exec -it ja /bin/sh //主机名与容器 id 一致
/ # hostname
7c230c5e540c
在容器启动时加入主机名
[root@docker ~]# docker run -it --name ha --hostname test --network bridge busybox
/ # hostname
test
/ # 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 test //注入主机名时会自动创建主机名到IP的映射关系
/ # cat /etc/resolv.conf //将网关设置成宿主机的网关
# Generated by NetworkManager
nameserver 192.168.58.2
// 注意在此之前如果关闭了宿主机防火墙，请打开，因为当宿主机上的防火墙关闭时，创建容器时，就不能够自动生成相应的防火墙规则到宿主机上，所以最后就会造成无法访问外网
/ # ping www.baidu.com
PING www.baidu.com (112.80.248.76): 56 data bytes
64 bytes from 112.80.248.76: seq=0 ttl=127 time=44.815 ms
64 bytes from 112.80.248.76: seq=1 ttl=127 time=41.081 ms
64 bytes from 112.80.248.76: seq=2 ttl=127 time=48.204 ms
--- www.baidu.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 41.081/44.700/48.204 ms
手动往/etc/hosts文件中注入主机名到IP地址的映射
[root@docker ~]# docker run -it --name gu --hostname mey --network bridge busybox
/ # vi /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.4 www.hubei.com
172.17.0.3 mey
开放容器端口
执行docker run的时候有个-p选项，可以将容器中的应用端口映射到宿主机中，从而实现让外部主机可以通过访问宿主机的某端口来访问容器内应用的目的。
-p选项能够使用多次，其所能够暴露的端口必须是容器确实在监听的端口。
-p选项的使用格式：
| -p < containerPort > | 将指定的容器端口映射至主机所有地址的一个动态端口 |
| -p < hostPort >:< containerPort > | 将容器端口映射至指定的主机端口 |
| -p < ip >::< containerPort > | 将指定的容器端口映射至主机指定的动态端口 |
| -p < ip >:< hostPort >:< containerPort > | 将指定的容器端口映射至主机指定的端口 |
动态端口指的是随机端口，具体的映射结果可使用docker port命令查看。
[root@docker ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
xm17671855780/ngin v0.2 25f7843775cf 41 hours ago 549MB
xm17671855780/nginx v0.1 178fc2a97021 42 hours ago 549MB
xm17671855780/php v0.1 bec4eea1d025 43 hours ago 1.46GB
xm17671855780/php v0.2 bec4eea1d025 43 hours ago 1.46GB
xm17671855780/mysql v0.1 1a3e53bdee96 45 hours ago 3.8GB
xm17671855780/mysql v0.2 1a3e53bdee96 45 hours ago 3.8GB
xm17671855780/i1 v0.3 8be6aa7baa79 2 days ago 549MB
xm17671855780/i1 v0.2 81869f360a9b 2 days ago 549MB
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
tomcat latest 904a98253fbf 2 weeks ago 680MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
[root@docker ~]# docker run -it --name nginx --rm -p 80 178fc2a97021
[root@a2b86e928f45 /]# ss -anlt
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 128 0.0.0.0:80 0.0.0.0:*
新开一个控制终端连接来看一下容器的80端口被映射到了宿主机的什么端口上
[root@docker ~]# docker ps -a //查看运行状态
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a2b86e928f45 178fc2a97021 "/bin/bash /start.sh" About a minute ago Up About a minute 0.0.0.0:49153->80/tcp, :::49153->80/tcp nginx
[root@docker ~]# ss -anlt
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 128 0.0.0.0:49153 0.0.0.0:*
LISTEN 0 128 [::]:22 [::]:*
LISTEN 0 128 [::]:49153 [::]:*
由此可见，容器的80端口被暴露到了宿主机的49153端口上，此时我们在宿主机上访问一下这个端口看是否能访问到容器内的站点
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>
[root@docker ~]#
因为做了nginx的端口映射，所以用宿主机的ip地址加上映射的随机端口也能访问到nginx页面
iptables防火墙规则将随容器的创建自动生成，随容器的删除自动删除规则。
将容器端口映射到指定IP的随机端口(在做端口映射之前 应开启防火墙，使其容器能够改变防火墙规则，放行端口)
[root@docker ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
xm17671855780/ngin v0.2 25f7843775cf 41 hours ago 549MB
xm17671855780/nginx v0.1 178fc2a97021 42 hours ago 549MB
xm17671855780/php v0.1 bec4eea1d025 43 hours ago 1.46GB
xm17671855780/php v0.2 bec4eea1d025 43 hours ago 1.46GB
xm17671855780/mysql v0.1 1a3e53bdee96 45 hours ago 3.8GB
xm17671855780/mysql v0.2 1a3e53bdee96 45 hours ago 3.8GB
xm17671855780/i1 v0.3 8be6aa7baa79 2 days ago 549MB
xm17671855780/i1 v0.2 81869f360a9b 2 days ago 549MB
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
tomcat latest 904a98253fbf 2 weeks ago 680MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
[root@docker ~]# docker run -it --name nginx --rm -p 192.168.58.10::80 8be6aa7baa79
[root@204ef8b9d70d /]# ss -anlt
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 128 0.0.0.0:80 0.0.0.0:*
在另一个终端上查看端口映射情况
[root@docker ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
204ef8b9d70d 8be6aa7baa79 "/bin/bash /start.sh" 22 seconds ago Up 16 seconds 192.168.58.10:49195->80/tcp nginx
网站访问
将容器端口映射到宿主机的指定端口
[root@docker ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
xm17671855780/ngin v0.2 25f7843775cf 41 hours ago 549MB
xm17671855780/nginx v0.1 178fc2a97021 42 hours ago 549MB
xm17671855780/php v0.1 bec4eea1d025 43 hours ago 1.46GB
xm17671855780/php v0.2 bec4eea1d025 43 hours ago 1.46GB
xm17671855780/mysql v0.1 1a3e53bdee96 45 hours ago 3.8GB
xm17671855780/mysql v0.2 1a3e53bdee96 45 hours ago 3.8GB
xm17671855780/i1 v0.3 8be6aa7baa79 2 days ago 549MB
xm17671855780/i1 v0.2 81869f360a9b 2 days ago 549MB
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
tomcat latest 904a98253fbf 2 weeks ago 680MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
[root@docker ~]# docker run -it --name nginx --rm -p 80:80 8be6aa7baa79
[root@86f0270dce50 /]# ss -anlt
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 128 0.0.0.0:80 0.0.0.0:*
在另一个终端上查看端口映射情况
[root@docker ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
86f0270dce50 8be6aa7baa79 "/bin/bash /start.sh" 2 minutes ago Up 2 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp nginx
[root@docker ~]# ss -anlt //主机上发现监听
State Recv-Q Send-Q Local Address:Port Peer Address:Port
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 128 [::]:80 [::]:*
LISTEN 0 128 [::]:22 [::]:*
[root@docker ~]# docker port nginx //查看端口映射情况
80/tcp -> 0.0.0.0:80
80/tcp -> :::80
用宿主机的IP网站测试
systemctl stop firewalld //访问时关闭防火墙
自定义docker0桥的网络属性信息
注意： 修改的网桥不能和自己的默认网卡网段一致（ens160 192.168.58.10）
自定义docker0桥的网络属性信息需要修改 /etc/docker/daemon.json配置文件
[root@docker ~]# vi /etc/docker/daemon.json
{
"registry-mirrors": ["https://a74l47xi.mirror.aliyuncs.com"],
"bip": "192.168.44.122/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: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0c:29:b7:b0:df brd ff:ff:ff:ff:ff:ff
inet 192.168.58.10/24 brd 192.168.58.255 scope global noprefixroute ens160
valid_lft forever preferred_lft forever
inet6 fe80::ca43:3f86:3176:184c/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:fb:e1:e1:9f brd ff:ff:ff:ff:ff:ff
inet 192.168.44.122/24 brd 192.168.44.255 scope global docker0
valid_lft forever preferred_lft forever
核心选项为bip，即bridge ip之意，用于指定docker0桥自身的IP地址；其它选项可通过此地址计算得出。
dockers远程连接
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.100.169:2375 ps
docker创建自定义桥
创建一个额外的自定义桥，区别于docker0
[root@docker ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
3d156462a29c bridge bridge local
f825718ae045 host host local
55b776caba23 none null local
[root@docker ~]# docker network create -d bridge --subnet "192.168.9.0/24" --gateway "192.168.9.1" br0
f1760fe939834c251498d10084389decb91de098a3f9af06006d07253883e3ce
[root@docker ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
f1760fe93983 br0 bridge local
3d156462a29c bridge bridge local
f825718ae045 host host local
55b776caba23 none null local
[root@docker ~]#
使用新创建的自定义桥来创建容器：
[root@docker ~]# docker run -it --name test --network br0 --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
13: eth0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue
link/ether 02:42:c0:a8:09:02 brd ff:ff:ff:ff:ff:ff
inet 192.168.9.2/24 brd 192.168.9.255 scope global eth0
valid_lft forever preferred_lft forever
// 此时我们发现新建的容器的ip为192.168.9.2
192.168.9.1 为网关
再创建一个容器，使用默认的bridge桥：
[root@docker ~]# docker run -it --name test1 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
17: eth0@if18: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue
link/ether 02:42:c0:a8:2c:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.44.1/24 brd 192.168.44.255 scope global eth0
valid_lft forever preferred_lft forever
发现这是刚刚修改后的docker0 的网段ip
试想一下，此时的test与test1能否互相通信？如果不能该如何实现通信？
我们可以把桥连接过去，br0是我们上传创建的，把默认桥连接到刚刚创建的创建的容器中
[root@docker ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
f1760fe93983 br0 bridge local
460702d0e47a bridge bridge local
f825718ae045 host host local
55b776caba23 none null local
[root@docker ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
027bd707cf91 busybox "sh" 5 minutes ago Up 5 minutes test1 // 默认桥
2325db3e17d6 busybox "sh" 9 minutes ago Up 9 minutes test
[root@docker ~]# docker network connect br0 027bd707cf91 //将test1 切换为br0
再到test1 容器中去ping192.168.9.2
/ # ping 192.168.9.2
PING 192.168.9.2 (192.168.9.2): 56 data bytes
64 bytes from 192.168.9.2: seq=0 ttl=64 time=0.571 ms
64 bytes from 192.168.9.2: seq=1 ttl=64 time=0.116 ms
64 bytes from 192.168.9.2: seq=2 ttl=64 time=0.221 ms
--- 192.168.9.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.116/0.302/0.571 ms
2961
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
