docker容器网络配置

最新推荐文章于 2024-05-23 10:01:42 发布

养了一只皮卡丘

最新推荐文章于 2024-05-23 10:01:42 发布

阅读量211

点赞数

分类专栏：容器文章标签： docker 容器网络

本文链接：https://blog.csdn.net/hyhxy0206/article/details/121738396

版权

容器专栏收录该内容

15 篇文章 3 订阅

订阅专栏

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

ip netns命令

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

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

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

[root@102 ~]# 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
[root@102 ~]# ip netns list

创建Network Namespace

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

[root@102 ~]# ip netns add ns0
[root@102 ~]# ip netns list
ns0

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

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

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

操作Network Namespace

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

//查看新创建 Network Namespace 的网卡信息
[root@102 ~]# 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

//可以看到，新创建的Network Namespace中会默认创建一个lo回环网卡，此时网卡处于关闭状态。
[root@102 ~]# ip netns exec ns0 ping 127.0.0.1
connect: 网络不可达

//up addr 等命令启用lo回环网卡：
[root@102 ~]# ip netns exec ns0 ip link set lo up 
[root@102 ~]# ip netns exec ns0 ip addr
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@102 ~]# 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.022 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.051 ms
^C
--- 127.0.0.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1026ms
rtt min/avg/max/mdev = 0.022/0.036/0.051/0.015 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@102 ~]# ip link add type veth
[root@102 ~]# ip a
...此上方有多行省略
4: veth0@veth1: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether a2:9a:60:80:65:dc 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 52:94:1c:af:ac:11 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@102 ~]# ip netns add ns1
[root@102 ~]# ip netns list
ns1
ns0
[root@102 ~]# ip netns exec ns0 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
[root@102 ~]# 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

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

//然后我们分别为这对veth pair配置上ip地址，并启用它们
[root@102 ~]# ip netns exec ns0 ip link set veth0 up
[root@102 ~]# ip netns exec ns0 ip addr add 192.168.143.100/24 dev veth0
[root@102 ~]# 
[root@102 ~]# ip netns exec ns1 ip link set veth1 up
[root@102 ~]# ip netns exec ns1 ip link set lo up
[root@102 ~]# ip netns exec ns1 ip addr add 192.168.143.100/24 dev veth1

//查看这对veth pair的状态
[root@102 ~]# ip netns exec ns0 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
4: veth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:9a:60:80:65:dc brd ff:ff:ff:ff:ff:ff link-netns ns1
    inet 192.168.143.100/24 scope global veth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a09a:60ff:fe80:65dc/64 scope link 
       valid_lft forever preferred_lft foreve       

[root@102 ~]# ip netns exec ns1 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
5: veth1@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 52:94:1c:af:ac:11 brd ff:ff:ff:ff:ff:ff link-netns ns0
    inet 192.168.143.100/24 scope global veth1
       valid_lft forever preferred_lft forever
    inet6 fe80::5094:1cff:feaf:ac11/64 scope link 
       valid_lft forever preferred_lft forever

//从上面可以看出，我们已经成功启用了这个veth pair，并为每个veth设备分配了对应的ip地址。我们尝试在ns1中访问ns0中的ip地址：
[root@102 ~]# ip netns exec ns1 ping 192.168.143.100
PING 192.168.143.100 (192.168.143.100) 56(84) bytes of data.
64 bytes from 192.168.143.100: icmp_seq=1 ttl=64 time=0.029 ms
64 bytes from 192.168.143.100: icmp_seq=2 ttl=64 time=0.042 ms
^C
--- 192.168.143.100 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1045ms
rtt min/avg/max/mdev = 0.029/0.035/0.042/0.008 ms
//可以看到，veth pair成功实现了两个不同Network Namespace之间的网络交互。

veth设备重命名

[root@102 ~]# ip netns exec ns0 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
4: veth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:9a:60:80:65:dc brd ff:ff:ff:ff:ff:ff link-netns ns1
    inet 192.168.143.100/24 scope global veth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a09a:60ff:fe80:65dc/64 scope link 
       valid_lft forever preferred_lft forever
[root@102 ~]# ip netns exec ns0 ip link set veth0 name eth0
RTNETLINK answers: Device or resource busy #设备或资源忙 （先停止）
[root@102 ~]# ip netns exec ns0 ip link set veth0 down
[root@102 ~]# ip netns exec ns0 ip link set veth0 name eth0
[root@102 ~]# ip netns exec ns0 ip link set eth0 up
[root@102 ~]# ip netns exec ns0 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
4: eth0@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:9a:60:80:65:dc brd ff:ff:ff:ff:ff:ff link-netns ns1
    inet 192.168.143.100/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::a09a:60ff:fe80:65dc/64 scope link 
       valid_lft forever preferred_lft forever

四种网络模式配置

bridge模式配置

[root@cf7d7d1c1cd4 /]# 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
[root@cf7d7d1c1cd4 /]# 
[root@cf7d7d1c1cd4 /]# exit
exit
//添加bridge无区别，bridge是默认docker的网络模式
[root@102 ~]#  docker run -it --name wbb --rm --network bridge centos
[root@96a978918b6f /]# 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模式配置

//nnone模式区别于，只有一个lo网卡
[root@102 ~]#  docker run -it --name wbb --rm --network none centos
[root@f2cdedae3848 /]# 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@102 ~]# docker run -it --name andd --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

//启动第二个容器
root@102 ~]# docker run -it --name angg --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: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
/ # exit

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

[root@102 ~]# docker run -it --name angg --rm --network container:andd 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

//此时我们在adnn容器上创建一个目录
到angg容器上检查/tmp目录会发现并没有这个目录，因为文件系统是处于隔离状态，仅仅是共享了网络而已。
/ # mkdir aidd
/ # ls 
aidd  bin   dev   etc   home  proc  root  sys   tmp   usr   var
//angg的容器
/ # ls 
bin   dev   etc   home  proc  root  sys   tmp   usr   var

//在andd容器上部署一个站点
/ # echo 'hello world' > /tmp/index.html
/ # ls /tmp/index.html 
/tmp/index.html
/ # netstat -atnl
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 :::80                   :::*                    LISTEN      
//在angg容器上用本地地址去访问此站点,由此可见，container模式下的容器间关系就相当于一台主机上的两个不同进程
/ # wget -O - -q 172.17.0.2:80
hello world

host模式配置

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

容器ip
[root@102 ~]# docker run -it --name andd --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:07:05:66 brd ff:ff:ff:ff:ff:ff
    inet 192.168.143.102/24 brd 192.168.143.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe07:566/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue 
    link/ether 02:42:b4:df:2c:b3 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:b4ff:fedf:2cb3/64 scope link 
       valid_lft forever preferred_lft forever
//主机ip
[root@102 ~]# 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:07:05:66 brd ff:ff:ff:ff:ff:ff
    inet 192.168.143.102/24 brd 192.168.143.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe07:566/64 scope link 
       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:b4:df:2c:b3 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:b4ff:fedf:2cb3/64 scope link 
       valid_lft forever preferred_lft forever
/ # echo 'hello world' > /tmp/index.html
/ # ls /tmp/
index.html
/ # httpd -h /tmp/    
/ # netstat -atnl |grep 80
tcp        0      0 :::80                   :::*                    LISTEN

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

容器的常用操作

查看容器的主机名

[root@102 ~]# docker run -it --name hy --rm busybox
/ # hostname
86fd58cbb18e
//查看容器ip 容器名
[root@102 ~]# docker container ls
CONTAINER ID   IMAGE     COMMAND   CREATED          STATUS          PORTS     NAMES
86fd58cbb18e   busybox   "sh"      24 seconds ago   Up 23 seconds             hy

在容器启动时注入主机名

[root@102 ~]# docker run -it --name hy --rm --hostname node1 busybox
/ # hostname
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.2	node1 # 注入主机名时会自动创建主机名到IP的映射关系
/ # cat /etc/resolv.conf 
# Generated by NetworkManager
nameserver 114.114.114.114 # DNS也会自动配置为宿主机的DNS
/ # ping www.baidu.com #可以联网
PING www.baidu.com (36.152.44.96): 56 data bytes
64 bytes from 36.152.44.96: seq=0 ttl=127 time=29.869 ms
64 bytes from 36.152.44.96: seq=1 ttl=127 time=30.602 ms
	64 bytes from 36.152.44.96: seq=2 ttl=127 time=30.435 ms
^C
--- www.baidu.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 29.869/30.302/30.602 ms

手动指定容器要使用的DNS

[root@102 ~]# docker run -it --name hy --rm --hostname node1 --dns 8.8.8.8 busybox
/ # cat /etc/resolv.conf 
nameserver 8.8.8.8

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

[root@102 ~]# docker run -it --name hy --rm --hostname node1 --add-host www.hh.com:8.8.8.8 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
8.8.8.8	www.hh.com
172.17.0.2	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@102 ~]# docker images
REPOSITORY         TAG       IMAGE ID       CREATED        SIZE
hyhxy0206/nginx1   v0.3      c169f5ef4e23   46 hours ago   549MB
hyhxy0206/php8     v0.2      2c937f1f1def   46 hours ago   1.52GB
hyhxy0206/mysql    v0.2      352b6f3c842c   47 hours ago   2.37GB
hyhxy0206/nginx1   v0.2      bcfc3da7190e   2 days ago     549MB
hyhxy0206/nginx1   v0.1      ccab9d297381   3 days ago     549MB
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@c3548d59d812 /]# ss -atnl
State   Recv-Q   Send-Q     Local Address:Port     Peer Address:Port  Process   
[root@c3548d59d812 /]# /usr/local/nginx/sbin/nginx 
[root@c3548d59d812 /]# ss -atnl
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@c3548d59d812 /]#

以上命令执行后会一直占用着前端，我们新开一个终端连接来看一下容器的80端口被映射到了宿主机的什么端口上

[root@102 ~]# docker port hy
80/tcp -> 0.0.0.0:49153
80/tcp -> :::49153

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

[root@102 ~]#  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防火墙规则将随容器的创建自动生成，随容器的删除自动删除规则。
[root@c3548d59d812 /]# exit
exit
[root@102 ~]# iptables -t nat -nvL
.....以上多行省略
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DOCKER     all  --  *      *       0.0.0.0/0           !127.0.0.0/8          ADDRTYPE match dst-type LOCAL

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 RETURN     all  --  docker0 *       0.0.0.0/0            0.0.0.0/0

将容器端口映射到指定IP的随机端口
[root@102 ~]#  docker run -it --name hy --rm -p 80:80 ccab9d297381
[root@ae3316257912 /]# /usr/local/nginx/sbin/nginx 
[root@ae3316257912 /]# ss -atnl
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@ae3316257912 /]#

在另一个终端上查看端口映射情况
[root@102 ~]# docker port hy
80/tcp -> 0.0.0.0:80
80/tcp -> :::80

//测试效果
[root@102 ~]#  curl http://127.0.0.1
<!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>

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

官方文档相关配置

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

{
    "bip": "192.168.1.5/24",
    "fixed-cidr": "192.168.1.5/25",
    "fixed-cidr-v6": "2001:db8::/64",
    "mtu": 1500,
    "default-gateway": "10.20.1.1",
    "default-gateway-v6": "2001:db8:abcd::89",
    "dns": ["10.20.1.2","10.20.1.3"]
}
//实例
[root@102 ~]# vim /etc/docker/daemon.json
{
    "bip": "192.168.1.5/24",       #核心选项为bip，即bridge ip之意，用于指定docker0桥自身的IP地址；其它选项可通过此地址计算得出。
    "dns":["10.20.1.2","10.20.1.3"],
    "registry-mirrors": ["https://xxxx.mirror.aliyuncs.com"]        #镜像加速器
}

[root@102 ~]# systemctl daemon-reload
[root@102 ~]# systemctl restart docker

[root@102 ~]# docker run -it --name hy --rm ccab9d297381
[root@d474dac00a86 /]# 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
26: eth0@if27: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
    link/ether 02:42:c0:a8:01:01 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 192.168.1.1/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever

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@102 ~]# docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
e1a6dd710dc7   bridge    bridge    local
f07e7613bacb   host      host      local
d951c3cc12d5   none      null      local
[root@102 ~]# docker network create -d bridge --subnet "192.168.24.0/24" --gateway "192.168.24.1" br0
2c38d533e3d5d27f5eeff4bf92fa008a7bf2adb3341e89bbca4f8ef8def4e65f
[root@102 ~]# docker ls
docker: 'ls' is not a docker command.
See 'docker --help'
[root@102 ~]# docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
2c38d533e3d5   br0       bridge    local
05e9de7da709   bridge    bridge    local
2af253d30cf8   host      host      local
433dfebbef06   none      null      local

//使用新创建的自定义桥来创建容器
[root@102 ~]# docker run -it --name hy --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
5: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue 
    link/ether 02:42:c0:a8:18:02 brd ff:ff:ff:ff:ff:ff
    inet 192.168.24.2/24 brd 192.168.24.255 scope global eth0
       valid_lft forever preferred_lft forever
/ # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.24.1    0.0.0.0         UG    0      0        0 eth0
192.168.24.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0

养了一只皮卡丘

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
docker容器网络配置

Linux内核实现名称空间的创建ip netns命令可以借助ip netns命令来完成对 Network Namespace 的各种操作。ip netns命令来自于iproute安装包，一般系统会默认安装，如果没有的话，请自行安装。注意：ip netns命令修改网络配置时需要 sudo 权限。可以通过ip netns命令完成对Network Namespace 的相关操作，可以通过ip netns help查看命令帮助信息：[root@102 ~]# ip netns helpUsage: ip
复制链接

扫一扫