正文

Docker入门篇（二）之docker的单主机网络

IP云
IP云V管理员/7 阅读
11/29
提示：扫一扫查出行
【扫一扫了解最新限行尾号】
复制提示

Docker 安装时会自动在 host 上创建三个网络，我们可用 docker network ls 命令查看： 

[root@localhost ~]# docker network ls

NETWORK ID          NAME                DRIVER              SCOPE

0164da7ee66a        bridge              bridge              local

a4a5d0b84564        host                host                local

df2c5c066a6a        none                null                local

1、host模式

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

演示：

[root@localhost ~]# docker run -it --rm --net=host --name net1 centos_1 bash

[root@localhost /]# ifconfig

docker0: flags=<UP,BROADCAST,MULTICAST>  mtu

        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0

        inet6 fe80:::5aff:fe52:25a9  prefixlen   scopeid 0x20<link>

        ether ::5a:::a9  txqueuelen   (Ethernet)

        RX packets   bytes  (43.7 MiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (291.6 MiB)

        TX errors   dropped  overruns   carrier   collisions 

enp0s3: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 192.168.0.165  netmask 255.255.255.0  broadcast 192.168.0.255

        inet6 fe80::71bd::36ed:a5df  prefixlen   scopeid 0x20<link>

        ether :::::d8  txqueuelen   (Ethernet)

        RX packets   bytes  (257.4 MiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (82.9 MiB)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (259.5 KiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (259.5 KiB)

        TX errors   dropped  overruns   carrier   collisions

2、container模式

container 模式，使用 --net=container:container_id/container_name 多个容器使用共同的网络，这个模式指定新创建的容器和已经存在的一个容器共享一个 Network Namespace ，而不是和宿主机共享。新创建的容器不会创建自己的网卡，配置自己的 IP ，而是和一个指定的容器共享 IP 、端口范围等。同样，两个容器除了网络方面，其他的如文件系统、进程列表等还是隔离的。两个容器的进程可以通过 lo 网卡设备通信。 

演示：

①创建一个net2的容器，并查看ip为172.17.0.

[root@localhost ~]# docker run -itd --name net2 centos_1 bash

b8a14e5e8a670d5680aae830f79267257143397c124d011fbf09b71c59b37e5d

[root@localhost ~]# docker exec -it net2 bash

[root@b8a14e5e8a67 /]# ifconfig

eth0: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 172.17.0.2  netmask 255.255.0.0  broadcast 0.0.0.0

        inet6 fe80:::acff:fe11:  prefixlen   scopeid 0x20<link>

        ether ::ac:::  txqueuelen   (Ethernet)

        RX packets   bytes  (648.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (648.0 B)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions 

②创建容器net3，并指定使用container网络模式，查看net3容器的ip为：172.17.0.2

[root@localhost ~]# docker run -it --net=container:net2 --name net3 centos_1 bash

[root@b8a14e5e8a67 /]# ifconfig

eth0: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 172.17.0.2  netmask 255.255.0.0  broadcast 0.0.0.0

        inet6 fe80:::acff:fe11:  prefixlen   scopeid 0x20<link>

        ether ::ac:::  txqueuelen   (Ethernet)

        RX packets   bytes  (648.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (648.0 B)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions 

③查看运行的net2，net3容器，两者id并不相同，但使用container网络模式，进入到net3时，net3容器id会和net2相同

[root@localhost ~]# docker ps

CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

a795f6825e1e        centos_1            "bash"               minutes ago       Up  seconds                            net3

b8a14e5e8a67        centos_1            "bash"               minutes ago       Up  minutes                            net2

[root@localhost ~]# docker exec -it net3 bash

[root@b8a14e5e8a67 /]# ifconfig

eth0: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 172.17.0.2  netmask 255.255.0.0  broadcast 0.0.0.0

        inet6 fe80:::acff:fe11:  prefixlen   scopeid 0x20<link>

        ether ::ac:::  txqueuelen   (Ethernet)

        RX packets   bytes  (648.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (648.0 B)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions

3、none模式

non e模式，使用 --net=none 指定这种模式下，不会配置任何网络。使用 none 模式， Docker 容器拥有自己的 Network Namespace ，但是，并不为 Docker 容器进行任何网络配置。也就是说，这个 Docker 容器没有 网卡、IP、路由 等信息。需要我们自己为 Docker 容器添加网卡、配置IP等。 

演示：

[root@localhost ~]# docker run -it --net=none --name net4 centos_1 bash

[root@b12e7ad03af2 /]# ifconfig

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions

4、bridge模式

bridge 模式，使用 --net=bridge 指定默认模式，当 Docker 进程启动时，会在主机上创建一个名为 docker0 的虚拟网桥，此主机上启动的 Docker 容器会连接到这个虚拟网桥上。虚拟网桥的工作方式和物理交换机类似，这样主机上的所有容器就通过交换机连在了一个二层网络中。

从 docker0 子网中分配一个 IP 给容器使用，并设置 docker0 的IP地址为容器的默认网关。在主机上创建一对虚拟网卡 veth pair 设备， Docker 将 veth pair 设备的一端放在新创建的容器中，并命名为 eth0 （容器的网卡），另一端放在主机中，以 vethxxx 这样类似的名字命名，并将这个网络设备加入到 docker0 网桥中。可以通过 brctl show 命令查看。

bridge 模式是docker的默认网络模式，不写 --net 参数，就是 bridge 模式。使用 docker run -p 时， docker 实际是在 iptables 做了DNAT规则，实现端口转发功能。可以使用 iptables -t nat -vnL 查看。 

演示：

①查看宿主机docker0的虚拟网桥ip为：172.17.0.1

[root@localhost ~]# ifconfig

docker0: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0

        inet6 fe80:::5aff:fe52:25a9  prefixlen   scopeid 0x20<link>

        ether ::5a:::a9  txqueuelen   (Ethernet)

        RX packets   bytes  (43.7 MiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (291.6 MiB)

        TX errors   dropped  overruns   carrier   collisions 

enp0s3: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 192.168.0.165  netmask 255.255.255.0  broadcast 192.168.0.255

        inet6 fe80::71bd::36ed:a5df  prefixlen   scopeid 0x20<link>

        ether :::::d8  txqueuelen   (Ethernet)

        RX packets   bytes  (258.7 MiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (83.1 MiB)

        TX errors   dropped  overruns   carrier   collisions 

②创建net5容器，并使用bridge网络模式。查看ip和网关

[root@localhost ~]# docker run -it --name net5 --net=bridge centos_1 bash

[root@a3a6416d08c0 /]# ifconfig

eth0: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 172.17.0.3  netmask 255.255.0.0  broadcast 0.0.0.0

        inet6 fe80:::acff:fe11:  prefixlen   scopeid 0x20<link>

        ether ::ac:::  txqueuelen   (Ethernet)

        RX packets   bytes  (508.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (508.0 B)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions

[root@a3a6416d08c0 /]# route -n

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

0.0.0.0         172.17.0.1      0.0.0.0         UG                   eth0

172.17.0.0      0.0.0.0         255.255.0.0     U                    eth0

5、如何自定义docker网络？

我们可通过 bridge 驱动创建类似前面默认的 bridge 网络，例如： 

[root@localhost ~]# docker network create --driver bridge my_net  #创建桥接网络my_net

afb854fd239b26f95265002190f9df88f8b7f66c204085bfd16c6a2b4932f5d9

[root@localhost ~]# brctl show   查看一下当前 host 的网络结构变化

bridge name bridge          id      STP enabled interfaces

br-afb854fd239b     .02422702f1bc   no

docker0             .0242646f882f   no      veth211fb49

                                                veth709c331

                                                veth8069764

                                                vethfa120d8
增了一个网桥 br-afb854fd239b，这里 br-afb854fd239b 正好新建 bridge 网络 my_net 的短 id。执行 docker network inspect 查看一下 my_net 的配置信息： 
[root@localhost ~]# docker network inspect my_net

[

    {

        "Name": "my_net",

        "Id": "afb854fd239b26f95265002190f9df88f8b7f66c204085bfd16c6a2b4932f5d9",

        "Created": "2018-04-21T14:14:15.479906429+08:00",

        "Scope": "local",

        "Driver": "bridge",

        "EnableIPv6": false,

        "IPAM": {

            "Driver": "default",

            "Options": {},

            "Config": [

                {

                    "Subnet": "172.18.0.0/16",  #这里 172.18.0.0/ 是 Docker 自动分配的 IP 网段。

                    "Gateway": "172.18.0.1"

                }

            ]

        },

        "Internal": false,

        "Attachable": false,

        "Containers": {},

        "Options": {},

        "Labels": {}

    }

]

指定 --subnet 和 --gateway 参数自定义 ip 网段： 

[root@localhost ~]# docker network create --driver bridge --subnet 192.168.100.0/ --gateway 192.168.100.1 my_net2

889ba4ceb97290e440db559e104db2bf9273854fd789322aaea30b3c76937af6

[root@localhost ~]# docker network inspect my_net2

[

    {

        "Name": "my_net2",

        "Id": "889ba4ceb97290e440db559e104db2bf9273854fd789322aaea30b3c76937af6",

        "Created": "2018-04-21T14:19:15.730480499+08:00",

        "Scope": "local",

        "Driver": "bridge",

        "EnableIPv6": false,

        "IPAM": {

            "Driver": "default",

            "Options": {},

            "Config": [

                {

                    "Subnet": "192.168.100.0/24",

                    "Gateway": "192.168.100.1"

                }

            ]

        },

        "Internal": false,

        "Attachable": false,

        "Containers": {},

        "Options": {},

        "Labels": {}

    }

]

创建了新的 bridge 网络 my_net2，网段为 192.168.100.0/24，网关为 192.168.100.1。与前面一样，网关在 my_net2 对应的网桥 br-889ba4ceb972 上： 

[root@localhost ~]# brctl show

bridge name bridge          id          STP enabled         interfaces

br-889ba4ceb972     .02424b2256df       no

br-afb854fd239b     .02422702f1bc       no

docker0             .0242646f882f       no              veth211fb49

                                                            veth709c331

                                                            veth8069764

                                                            vethfa120d8

[root@localhost ~]# ifconfig br-889ba4ceb972

br-889ba4ceb972: flags=<UP,BROADCAST,MULTICAST>  mtu

        inet 192.168.100.1  netmask 255.255.255.0  broadcast 0.0.0.0

        ether ::4b:::df  txqueuelen   (Ethernet)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions

容器要使用新的网络，需要在启动时通过 --network 指定，并且还可以使用 --ip 参数直接指定一个静态 ip ： 

[root@localhost ~]# docker run -it --network=my_net2 busybox

/ # ip a

: lo: <LOOPBACK,UP,LOWER_UP> mtu  qdisc noqueue qlen

    link/loopback ::::: brd :::::

    inet 127.0.0.1/ scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::/ scope host

       valid_lft forever preferred_lft forever

: eth0@if117: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu  qdisc noqueue

    link/ether ::c0:a8:: brd ff:ff:ff:ff:ff:ff

    inet 192.168.100.2/ scope global eth0   ##容器被分配的ip为192.168.100.

       valid_lft forever preferred_lft forever

    inet6 fe80:::c0ff:fea8:/ scope link

       valid_lft forever preferred_lft forever

[root@localhost ~]# docker run -it --network=my_net2 --ip 192.168.100.100 busybox

/ # ip a

: lo: <LOOPBACK,UP,LOWER_UP> mtu  qdisc noqueue qlen

    link/loopback ::::: brd :::::

    inet 127.0.0.1/ scope host lo

       valid_lft forever preferred_lft forever

    inet6 ::/ scope host

       valid_lft forever preferred_lft forever

: eth0@if119: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu  qdisc noqueue

    link/ether ::c0:a8:: brd ff:ff:ff:ff:ff:ff

    inet 192.168.100.100/ scope global eth0    ##容器被分配的ip为192.168.100.

       valid_lft forever preferred_lft forever

    inet6 fe80:::c0ff:fea8:/ scope link

       valid_lft forever preferred_lft forever

注：只有使用 --subnet 创建的网络才能指定静态 IP。

my_net 创建时没有指定 --subnet，如果指定静态 IP 报错如下：

[root@localhost ~]# docker run -it --rm --network=my_net --ip 172.18.0.100 busybox

/usr/bin/docker-current: Error response from daemon: User specified IP address is supported only when connecting to networks with user configured subnets.

6、Docker使用pipework配置容器与宿主机在同一网段

为了使本地网络中的机器和 Docker 容器更方便的通信，我们经常会有将 Docker 容器配置到和主机同一网段的需求。这个需求其实很容易实现，我们只要将 Docker 容器和宿主机的网卡桥接起来，再给 Docker 容器配上 IP 就可以了。

（1）新建桥接网卡br0，并进行修改宿主机网卡enp0s3以及br0 

[root@localhost network-scripts]# cp ifcfg-enp0s3 ifcfg-br0

[root@localhost network-scripts]# vim ifcfg-br0

注：修改TYPE=Bridge,DEVICE=br0,NAME=br0

TYPE=Bridge

BOOTPROTO=static

DEFROUTE=yes

PEERDNS=yes

PEERROUTES=yes

IPV4_FAILURE_FATAL=no

IPV6INIT=yes

IPV6_AUTOCONF=yes

IPV6_DEFROUTE=yes

IPV6_PEERDNS=yes

IPV6_PEERROUTES=yes

IPV6_FAILURE_FATAL=no

IPV6_ADDR_GEN_MODE=stable-privacy

NAME=br0

#UUID=faa61166-b507--b055-2c6284de3981

DEVICE=br0

ONBOOT=yes

IPADDR=192.168.0.165

GATEWAY=192.168.0.1

NATMASK=255.255.255.0

DNS1=8.8.8.8

#NM_CONTROLLED=no

[root@localhost network-scripts]# vim ifcfg-enp0s3

注：增加BRIDGE=br0，删除IPADDR,GATEWAY,NETMASK,DNS

TYPE=Ethernet

BOOTPROTO=static

DEFROUTE=yes

PEERDNS=yes

PEERROUTES=yes

IPV4_FAILURE_FATAL=no

IPV6INIT=yes

IPV6_AUTOCONF=yes

IPV6_DEFROUTE=yes

IPV6_PEERDNS=yes

IPV6_PEERROUTES=yes

IPV6_FAILURE_FATAL=no

IPV6_ADDR_GEN_MODE=stable-privacy

NAME=enp0s3

#UUID=faa61166-b507--b055-2c6284de3981

DEVICE=enp0s3

ONBOOT=yes

#IPADDR=192.168.0.165

#GATEWAY=192.168.0.1

#NATMASK=255.255.255.0

#DNS1=8.8.8.8

#NM_CONTROLLED=no

BRIDGE=br0

（2）重启网络，查看br0的ip地址，以及enp0s3是否未分配ip地址，表示成功 

[root@localhost network-scripts]# systemctl restart network

[root@localhost network-scripts]# ifconfig

br0: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 192.168.0.165  netmask 255.255.255.0  broadcast 192.168.0.255

        inet6 fe80::ca01:a411:fb77:c348  prefixlen   scopeid 0x20<link>

        ether :::::d8  txqueuelen   (Ethernet)

        RX packets   bytes  (3.4 KiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (2.2 KiB)

        TX errors   dropped  overruns   carrier   collisions 

docker0: flags=<UP,BROADCAST,MULTICAST>  mtu

        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0

        ether ::7e:ec:e1:e6  txqueuelen   (Ethernet)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions 

enp0s3: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        ether :::::d8  txqueuelen   (Ethernet)

        RX packets   bytes  (314.1 KiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (178.2 KiB)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (7.7 KiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (7.7 KiB)

        TX errors   dropped  overruns   carrier   collisions

（3）下载pipework 

[root@localhost ~]# git clone https://github.com/jpetazzo/pipework

Cloning into 'pipework'...

remote: Counting objects: , done.

remote: Total  (delta ), reused  (delta ), pack-reused

Receiving objects: % (/), 172.97 KiB | 4.00 KiB/s, done.

Resolving deltas: % (/), done.

（4）拷贝pipework二进制文件到/usr/local/bin下，运行一个容器并使用none网络模式 

[root@localhost ~]# cp pipework/pipework /usr/local/bin/

[root@localhost ~]# docker run -itd --net=none --name pipework centos_nginx bash

ab88e2159ce32408154a776c1c62cf1af170fa8ce4d01908da6175f01b6c787d

[root@localhost ~]# docker ps

CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

ab88e2159ce3        centos_nginx        "bash"               seconds ago       Up  seconds                            pipework

[root@localhost ~]# docker exec -it pipework bash

[root@ab88e2159ce3 /]# ifconfig

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions

[root@ab88e2159ce3 /]# exit

exit

（5）使用pipework进行配置容器pipework的ip地址，166为容器的ip地址，@后面的ip为容器网关，配置完毕进入容器进行查看 

[root@localhost ~]# pipework br0 pipework 192.168.0.166/@192.168.0.1

[root@localhost ~]# docker exec -it pipework bash

[root@ab88e2159ce3 /]# ifconfig

eth1: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 192.168.0.166  netmask 255.255.255.0  broadcast 192.168.0.255

        inet6 fe80::340c:ebff:fe50:1ba3  prefixlen   scopeid 0x20<link>

        ether :0c:eb::1b:a3  txqueuelen   (Ethernet)

        RX packets   bytes  (10.2 KiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (732.0 B)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions

（6）windows和linux下验证容器pipework的网络连通性 

[root@ab88e2159ce3 /]# ping www.baidu.com

PING www.a.shifen.com (14.215.177.39) () bytes of data.

 bytes from 14.215.177.39 (14.215.177.39): icmp_seq= ttl= time=8.29 ms

 bytes from 14.215.177.39 (14.215.177.39): icmp_seq= ttl= time=8.09 ms

 bytes from 14.215.177.39 (14.215.177.39): icmp_seq= ttl= time=8.43 ms

 bytes from 14.215.177.39 (14.215.177.39): icmp_seq= ttl= time=8.12 ms

 bytes from 14.215.177.39 (14.215.177.39): icmp_seq= ttl= time=8.80 ms

 bytes from 14.215.177.39 (14.215.177.39): icmp_seq= ttl= time=8.51 ms

^C

--- www.a.shifen.com ping statistics ---

 packets transmitted,  received, % packet loss, time 5007ms

rtt min/avg/max/mdev = 8.094/8.378/8.805/0.249 ms

（7）通过pipework配置网络，配置web服务 

[root@localhost ~]# docker run -itd --privileged -e "container=docker" --name pipework --net=none centos_nginx /usr/sbin/init

aa85a59dc347633fcd9a2b5206eaed619451c52f299d2505c32df2b6d1ce7521

[root@localhost ~]# pipework br0 pipework 192.168.0.166/@192.168.0.1

[root@localhost ~]# docker exec -it pipework bash

[root@aa85a59dc347 /]# ifconfig

eth1: flags=<UP,BROADCAST,RUNNING,MULTICAST>  mtu

        inet 192.168.0.166  netmask 255.255.255.0  broadcast 192.168.0.255

        inet6 fe80::a00d:aff:fec2:a59d  prefixlen   scopeid 0x20<link>

        ether a2:0d:0a:c2:a5:9d  txqueuelen   (Ethernet)

        RX packets   bytes  (20.6 KiB)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (774.0 B)

        TX errors   dropped  overruns   carrier   collisions 

lo: flags=<UP,LOOPBACK,RUNNING>  mtu

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::  prefixlen   scopeid 0x10<host>

        loop  txqueuelen   (Local Loopback)

        RX packets   bytes  (0.0 B)

        RX errors   dropped   overruns   frame

        TX packets   bytes  (0.0 B)

        TX errors   dropped  overruns   carrier   collisions 

[root@aa85a59dc347 /]# systemctl start nginx

[root@aa85a59dc347 /]# netstat -tulnp |grep nginx

tcp               0.0.0.0:              0.0.0.0:*               LISTEN      /nginx: master pr

tcp6              :::                   :::*                    LISTEN      /nginx: master pr

[root@aa85a59dc347 /]# ps -ef |grep nginx

root                : ?        :: nginx: master process /usr/sbin/nginx

nginx              : ?        :: nginx: worker process

root               : ?        :: grep --color=auto nginx

相关阅读

目录[+]