1 Linux内核实现名称空间的创建
1.1 ipnets命令
- 可以借助ip netns命令来完成对 Network Namespace 的各种操作。ip netns命令来自于iproute安装包,一般系统会默认安装,如果没有的话,请自行安装。
[root@docker ~]# yum -y install 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 [target-nsid POSITIVE-INT] [nsid POSITIVE-INT]
NETNSID := auto | POSITIVE-INT
默认情况下,Linux系统中是没有任何 Network Namespace的,所以ip netns list
命令不会返回任何信息。
1.2 创建Network Namespace
通过命令创建一个名为nb0的命名空间:
[root@docker ~]# ip netns list
[root@docker ~]# ip netns add nb0
[root@docker ~]# ip netns list
nb0
[root@docker ~]#
新创建的 Network Namespace 会出现在/var/run/netns/目录下
。如果相同名字的 namespace 已经存在,命令会报Cannot create namespace file "/var/run/netns/ns0": File exists
的错误。
[root@docker ~]# cd /var/run/netns/
[root@docker netns]# ls
nb0
[root@docker netns]# ip netns add nb0
Cannot create namespace file "/var/run/netns/nb0": File exists
[root@docker netns]#
- 对于每个 Network Namespace 来说,它会有自己
独立的网卡、路由表、ARP 表、iptables 等和网络相关的资源
。
1.3 操作Network Namespace
ip命令提供了ip netns exec
子命令可以在对应的 Network Namespace 中执行命令。
查看新创建 Network Namespace 的网卡信息
[root@docker ~]# ip netns exec nb0 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@docker ~]#
可以看到,新创建的Network Namespace中会默认创建一个lo回环网卡,此时网卡处于关闭状态。此时,尝试去 ping 该lo回环网卡,会提示Network is unreachable(网络不可达)
[root@docker ~]# ip netns exec nb0 ping 127.0.0.1
connect: 网络不可达
[root@docker ~]#
通过下面的命令启用lo回环网卡:
[root@docker ~]# ip netns exec nb0 ip link set lo up
[root@docker ~]# ip netns exec nb0 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.027 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.020 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.026 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.029 ms
1.4 转移设备
-
我们可以在不同的 Network Namespace 之间转移设备(如veth)。由于一个设备只能属于一个 Network Namespace ,所以转移后在这个 Network Namespace 内就看不到这个设备了。
-
其中,veth设备属于可转移设备,而很多其它设备
(如lo、vxlan、ppp、bridge等)
是不可以转移的。
1.4.1 veth pair
- veth pair 全称是 Virtual Ethernet Pair,是一个成对的端口,所有从这对端口一 端进入的数据包都将从另一端出来,反之也是一样。
- 引入veth pair是为了在不同的 Network Namespace 直接进行通信,利用它可以直接将两个 Network Namespace 连接起来。
1.4.2 创建veth pair
[root@docker ~]# ip link add type veth
[root@docker ~]# ip a
8: veth0@veth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether d2:70:07:3d:30:9d brd ff:ff:ff:ff:ff:ff
9: veth1@veth0: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether b2:c6:e8:6c:eb:f4 brd ff:ff:ff:ff:ff:ff
可以看到,此时系统中新增了一对veth pair,将veth0和veth1两个虚拟网卡连接了起来,此时这对 veth pair 处于”未启用“状态。
1.5 实现Network Namespace间通信
下面我们利用veth pair实现两个不同的 Network Namespace 之间的通信。刚才我们已经创建了一个名为nb0的 Network Namespace,下面再创建一个信息Network Namespace,命名为nb1
[root@docker ~]# ip netns add nb1
[root@docker ~]# ip netns list
nb1
nb0
[root@docker ~]#
然后我们将veth0加入到ns0,将veth1加入到ns1
[root@docker ~]# ip link set veth0 netns nb0
[root@docker ~]# ip link set veth1 netns nb1
[root@docker ~]#
然后我们分别为这对veth pair配置上ip地址,并启用它们
[root@docker ~]# ip netns exec nb0 ip link set veth0 up
[root@docker ~]# ip netns exec nb0 ip addr add 192.168.200.10/24 dev veth0
[root@docker ~]# ip netns exec nb1 ip link set veth1 up
[root@docker ~]# ip netns exec nb1 ip addr add 192.168.200.11/24 dev veth1
[root@docker ~]#
查看这对veth pair的状态
[root@docker ~]# ip netns exec nb0 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
8: veth0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether d2:70:07:3d:30:9d brd ff:ff:ff:ff:ff:ff link-netns nb1
inet 192.168.200.10/24 scope global veth0
valid_lft forever preferred_lft forever
inet6 fe80::d070:7ff:fe3d:309d/64 scope link
valid_lft forever preferred_lft forever
[root@docker ~]# ip netns exec nb1 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
9: veth1@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether b2:c6:e8:6c:eb:f4 brd ff:ff:ff:ff:ff:ff link-netns nb0
inet 192.168.200.11/24 scope global veth1
valid_lft forever preferred_lft forever
inet6 fe80::b0c6:e8ff:fe6c:ebf4/64 scope link
valid_lft forever preferred_lft forever
[root@docker ~]#
从上面可以看出,我们已经成功启用了这个veth pair,并为每个veth设备分配了对应的ip地址。我们尝试在nb1中访问nb0中的ip地址:
[root@docker ~]# ip netns exec nb1 ping 192.168.200.10
PING 192.168.200.10 (192.168.200.10) 56(84) bytes of data.
64 bytes from 192.168.200.10: icmp_seq=1 ttl=64 time=0.034 ms
64 bytes from 192.168.200.10: icmp_seq=2 ttl=64 time=0.023 ms
64 bytes from 192.168.200.10: icmp_seq=3 ttl=64 time=0.024 ms
64 bytes from 192.168.200.10: icmp_seq=4 ttl=64 time=0.026 ms
[root@docker ~]# ip netns exec nb0 ping 192.168.200.11
PING 192.168.200.11 (192.168.200.11) 56(84) bytes of data.
64 bytes from 192.168.200.11: icmp_seq=1 ttl=64 time=0.023 ms
64 bytes from 192.168.200.11: icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from 192.168.200.11: icmp_seq=3 ttl=64 time=0.023 ms
64 bytes from 192.168.200.11: icmp_seq=4 ttl=64 time=0.024 ms
可以看到,veth pair成功实现了两个不同Network Namespace之间的网络交互。
1.6 veth设备重命名
[root@docker ~]# ip netns exec nb0 ip link set veth0 down
[root@docker ~]# ip netns exec nb0 ip link set dev veth0 name ens0
[root@docker ~]# ip netns exec nb0 ip link set ens0 up
[root@docker ~]# ip netns exec nb0 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
8: ens0@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether d2:70:07:3d:30:9d brd ff:ff:ff:ff:ff:ff link-netns nb1
inet 192.168.200.10/24 scope global ens0
valid_lft forever preferred_lft forever
inet6 fe80::d070:7ff:fe3d:309d/64 scope link
valid_lft forever preferred_lft forever
[root@docker ~]#
2 四种网络模式配置
2.1 bridge模式配置
[root@docker ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
caiaoc/mysql v1.0 ba85e9d47f00 29 hours ago 3.81GB
caiaoc/nginx v1.0 a985a6973aec 29 hours ago 549MB
caiaoc/php v1.0 f5fe6827f02b 30 hours ago 1.46GB
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
[root@docker ~]#
[root@docker ~]# docker run -idt --name a1 --rm d23834f29b38
0076e75d191add6c13f1e52d282f3de92ab52bb5c024e80ee4db69e681991bb0
[root@docker ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0076e75d191a d23834f29b38 "sh" 7 seconds ago Up 6 seconds a1
[root@docker ~]# docker exec -it 0076e75d191a /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: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 ~]#
[root@docker ~]# docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
0076e75d191a d23834f29b38 "sh" 4 minutes ago Up 4 minutes a1
在创建容器时添加–network bridge与不加–network选项效果是一样的
[root@docker ~]# docker run -itd --name by --rm --network bridge d23834f29b38 /bin/sh
38a6a672a681c695b26e2175583d0be954c6966279a7a2a844612753ed534877
[root@docker ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
38a6a672a681 d23834f29b38 "/bin/sh" 19 seconds ago Up 18 seconds by
[root@docker ~]# docker exec -it 38a6a672a681 /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
14: eth0@if15: <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
/ #
2. 2 none模式
[root@docker ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
caiaoc/mysql v1.0 ba85e9d47f00 29 hours ago 3.81GB
caiaoc/nginx v1.0 a985a6973aec 30 hours ago 549MB
caiaoc/php v1.0 f5fe6827f02b 30 hours ago 1.46GB
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
[root@docker ~]# docker run -it --name a1 --network none --rm d23834f29b38
/ # 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
/ #
2.3 container模式配置
启动第一个容器
[root@docker ~]# docker run -it --name a1 --rm d23834f29b38
/ # 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: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
/ #
启动第二个容器
[root@docker ~]# docker run -it --name a2 --rm a985a6973aec
[root@c05253a893c6 /]# 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
24: eth0@if25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0
valid_lft forever preferred_lft forever
[root@c05253a893c6 /]#
可以看到名为a2的容器IP地址是172.17.0.3,与第一个容器的IP地址不是一样的,也就是说并没有共享网络,此时如果我们将第二个容器的启动方式改变一下,就可以使名为a2的容器IP与a1容器IP一致,也即共享IP,但不共享文件系统
。
[root@docker ~]# docker images
\REPOSITORY TAG IMAGE ID CREATED SIZE
caiaoc/mysql v1.0 ba85e9d47f00 30 hours ago 3.81GB
caiaoc/nginx v1.0 a985a6973aec 30 hours ago 549MB
caiaoc/php v1.0 f5fe6827f02b 30 hours ago 1.46GB
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
[root@docker ~]#
//再次创建一个容器b1,后面跟着的容器ID为你自定义想创建的容器ID,
//我这里为busybox容器ID,也就相当于我要创建一个b1容器使用container模式和a1共用一个IP
[root@docker ~]# docker run -it --name b1 --rm --network container:a1 d23834f29b38
/ # 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
26: eth0@if27: <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
/ #
此时我们在b1上的/usr目录下创建一个abc目录
/ # mkdir /usr/abc
/ # ls /usr/
abc sbin
/ #
到a1容器上检查/usr目录会发现并没有这个目录,因为文件系统是处于隔离状态,仅仅是共享了网络而已。
/ # ls /usr/
sbin
/ #
在b1容器上部署一个站点
/ # echo "this is test file " > /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
/ #
在a1容器上用本地地址去访问此站点
/ # wget -qO - 127.0.0.1
this is test file
/ #
由此可见,container模式下的容器间关系就相当于一台主机上的两个不同进程
2.3 host模式配置
启动容器时直接指明模式为host
[root@docker ~]# docker run -it --name b1 --rm --network host d23834f29b38
/ # 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:e1:a0:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.200.145/24 brd 192.168.200.255 scope global dynamic noprefixroute ens33
valid_lft 919sec preferred_lft 919sec
inet6 fe80::2490:d5ac:f553:e827/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
link/ether 02:42:83:80:23:97 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:83ff:fe80:2397/64 scope link
valid_lft forever preferred_lft forever
/ #
此时如果我们在这个容器中启动一个http站点,我们就可以直接用宿主机的IP直接在浏览器中访问这个容器中的站点了。
/ # echo "this is test page " > /tmp/index.html
/ # httpd -h /tmp/
/ #
4 容器的常用操作
4.1 查看容器的主机名
[root@docker ~]# docker run -it --name b1 --rm d23834f29b38
/ # hostname
bdb076c163df //可以发现,主机名和容器ID一致
/ #
[root@docker ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bdb076c163df d23834f29b38 "sh" 28 seconds ago Up 26 seconds b1
[root@docker ~]#
4.2 在容器启动时加入主机名
[root@docker ~]# docker run -it --name aa --rm --network bridge --hostname xixi d23834f29b38
/ # hostname
xixi
/ #
/ # 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 xixi //加入主机名时会自动创建主机名到IP的映射关系
/ # cat /etc/resolv.conf
# Generated by NetworkManager
search localdomain
nameserver 192.168.200.2 //DNS也会自动配置为宿主机的DNS
/ #
/ # ping www.baidu.com /这里也是可以ping通外网的
PING www.baidu.com (112.80.248.75): 56 data bytes
64 bytes from 112.80.248.75: seq=0 ttl=127 time=43.118 ms
64 bytes from 112.80.248.75: seq=1 ttl=127 time=152.571 ms
64 bytes from 112.80.248.75: seq=2 ttl=127 time=44.077 ms
4.3 手动往/etc/hosts文件中注入主机名到IP地址的映射
[root@docker ~]# docker run -it --name test1 --network bridge --hostname haha --add-host www.abc.com:1.1.1.1 --rm d23834f29b38
/ # 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.abc.com
172.17.0.2 haha
/ #
4.4 开放容器端口
执行docker run的时候有个-p选项,可以将容器中的应用端口映射到宿主机中,从而实现让外部主机可以通过访问宿主机的某端口来访问容器内应用的目的。
-p选项能够使用多次,其所能够暴露的端口必须是容器确实在监听的端口。
-p选项的使用格式:
- -p 【containerPort】
将指定的容器端口映射至主机所有地址的一个动态端口 - -p 【hostPort>:<containerPort】
将容器端口[containerPort]映射至指定的主机端口[hostPort] - -p [ip]::[containerPort]
将指定的容器端口映射至主机指定的动态端口 - -p [ip]:[hostPort]:[containerPort]
将指定的容器端口映射至主机指定的端口
4.4.1动态端口
指的是随机端口,具体的映射结果可使用docker port命令查看。
[root@docker ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
caiaoc/mysql v1.0 ba85e9d47f00 31 hours ago 3.81GB
caiaoc/nginx v1.0 a985a6973aec 31 hours ago 549MB
caiaoc/php v1.0 f5fe6827f02b 32 hours ago 1.46GB
busybox latest d23834f29b38 5 days ago 1.24MB
httpd latest ad17c88403e2 2 weeks ago 143MB
nginx latest ea335eea17ab 2 weeks ago 141MB
centos latest 5d0da3dc9764 2 months ago 231MB
[root@docker ~]# docker run -it --name nginx01 --rm -p 80 a985a6973aec
[root@524a260a4db3 /]#
以上命令执行后会一直占用着前端,我们新开一个终端连接来看一下容器的80端口被映射到了宿主机的什么端口上
[root@docker ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
524a260a4db3 a985a6973aec "/bin/bash /start.sh" 43 seconds ago Up 42 seconds 0.0.0.0:49153->80/tcp, :::49153->80/tcp nginx01
[root@docker ~]# docker port nginx01
80/tcp -> 0.0.0.0:49153
80/tcp -> :::49153
[root@docker ~]#
由此可见,容器的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>
[root@docker ~]#
因为做了nginx的端口映射,所以用宿主机的ip地址加上映射的随机端口也能访问到nginx页面
4.4.2 iptables防火墙规则
将随容器的创建自动生成,随容器的删除自动删除规则。
将容器端口映射到指定IP的随机端口
[root@docker ~]# docker run -it --name nginx02 --rm -p 192.168.200.145::80 a985a6973aec
[root@b4bc1a7605ab /]#
在另一个终端上查看端口映射情况
root@docker ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
b4bc1a7605ab a985a6973aec "/bin/bash /start.sh" 10 seconds ago Up 9 seconds 192.168.200.145:49153->80/tcp nginx02
[root@docker ~]#
4.4.3将容器端口映射到宿主机的指定端口
[root@docker ~]# docker run -it --name nginx03 --rm -p 80:80 a985a6973aec
[root@1a9bfdfe8c7d /]#
在另一个终端上查看端口映射情况
[root@docker ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1a9bfdfe8c7d a985a6973aec "/bin/bash /start.sh" 32 seconds ago Up 31 seconds 0.0.0.0:80->80/tcp, :::80->80/tcp nginx03
[root@docker ~]#
用宿主机的IP网站测试,注意这里不需要跟80端口
4.5 自定义docker0桥的网络属性信息
官方文档相关配置
自定义docker0桥的网络属性信息需要修改/etc/docker/daemon.json
配置文件
[root@docker ~]# vi /etc/docker/daemon.json
[root@docker ~]# cat /etc/docker/daemon.json
{
"registry-mirrors": ["https://l6paj5i1.mirror.aliyuncs.com"],
"bip": "192.168.10.5/24" //这里IP网段不能和网段本机IP相同
}
[root@docker ~]#
[root@docker ~]# systemctl start docker
[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:e1:a0:bf brd ff:ff:ff:ff:ff:ff
inet 192.168.200.145/24 brd 192.168.200.255 scope global dynamic noprefixroute ens33
valid_lft 1514sec preferred_lft 1514sec
inet6 fe80::2490:d5ac:f553:e827/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:fc:f6:59:d7 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.5/24 brd 192.168.10.255 scope global docker0
valid_lft forever preferred_lft forever
[root@docker ~]#
核心选项为bip,即bridge ip
之意,用于指定docker0桥自身的IP地址;其它选项可通过此地址计算得出。
4.6 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.200.145:2375 ps
- 这种方式现在基本上不怎么用,很少说用dockers远程连接去控制,所以了解一下就可以了,知道有这么一个功能就可以了
4.6 docker创建自定义桥
创建一个额外的自定义桥,区别于docker0
[root@docker ~]# docker network create -d bridge --subnet "192.168.3.0/24" --gateway "192.168.3.1" br0
58b49eb5e468b8978f7cc62fe7ab288346b40ae3f7ebe9015f57446c65c95f95
[root@docker ~]# docker network ls
NETWORK ID NAME DRIVER SCOPE
58b49eb5e468 br0 bridge local
cc5301d43460 bridge bridge local
c5372c67d91d host host local
7094ca2195a3 none null local
[root@docker ~]#
创建一个容器,使用默认的bridge桥:
[root@docker ~]# docker run -it --name b1 --rm d23834f29b38
/ # 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
5: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue
link/ether 02:42:c0:a8:0a:01 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 brd 192.168.10.255 scope global eth0 //这里IP是默认docker0分配的IP
valid_lft forever preferred_lft forever
/ #
再创建一个容器,使用的br0桥:
[root@docker ~]# docker run -it --name cc --rm --network br0 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:c0:a8:03:02 brd ff:ff:ff:ff:ff:ff
inet 192.168.3.2/24 brd 192.168.3.255 scope global eth0
valid_lft forever preferred_lft forever
/ #