Docker网络的none和host(17)
2019-03-04 17:22
447 查看
一、none
1、新建容器test3连接到none
[code][root@localhost ~]# docker run -it -d --name test3 --network none python 465ba8498be7bdf88cfe77054c14b943a7895833051db2902c9e7dba9adc82f1
2、查看none,会发现容器test3没有任何IP地址,相当于是完全孤立
[code][root@localhost ~]# docker network inspect none [ { "Name": "none", "Id": "7ed63a8db0963c5570ff468df94e0ef2b6f14e07c584bd544ab58b9b91114504", "Created": "2019-02-14T01:53:32.909743191-05:00", "Scope": "local", "Driver": "null", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "465ba8498be7bdf88cfe77054c14b943a7895833051db2902c9e7dba9adc82f1": { "Name": "test3", "EndpointID": "c0d3b93a85193f1e63b54e6fbbca0a20c886a85e831f7c1de4382 d541f483081", "MacAddress": "", "IPv4Address": "", "IPv6Address": "" } }, "Options": {}, "Labels": {} } ]
3、
[code][root@localhost ~]# docker exec -it test3 /bin/sh # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default ql en 1 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
二、host
1、新建容器test4连接到none
[code][root@localhost ~]# docker run -it -d --name test4 --network host python 17ad1fba02f30c446ff3fbe331e251efdd26ed3e46a4c47467a3e4825358db37
2、ip a,会发现容器test4是与宿主机共享网络的,这容易导致端口冲突
[code][root@localhost ~]# docker exec -it test4 /bin/sh # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default ql en 1 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: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP grou p default qlen 1000 link/ether 08:00:27:86:e3:e7 brd ff:ff:ff:ff:ff:ff inet 192.168.13.220/21 brd 192.168.15.255 scope global dynamic enp0s3 valid_lft 22616sec preferred_lft 22616sec inet6 fe80::f8da:1de:daac:3ce0/64 scope link valid_lft forever preferred_lft forever 3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN gro up default qlen 1000 link/ether 52:54:00:7f:90:e1 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state D OWN group default qlen 1000 link/ether 52:54:00:7f:90:e1 brd ff:ff:ff:ff:ff:ff 5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default link/ether 02:42:80:45:7a:69 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:80ff:fe45:7a69/64 scope link valid_lft forever preferred_lft forever 6: br-7d34e6c0f687: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state U P group default link/ether 02:42:4f:ee:0a:fb brd ff:ff:ff:ff:ff:ff inet 172.18.0.1/16 brd 172.18.255.255 scope global br-7d34e6c0f687 valid_lft forever preferred_lft forever inet6 fe80::42:4fff:feee:afb/64 scope link valid_lft forever preferred_lft forever 10: vethf0c60b2@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-7d34e6c0f687 state UP group default link/ether c2:cb:5d:97:0a:36 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fe80::c0cb:5dff:fe97:a36/64 scope link valid_lft forever preferred_lft forever 12: vethdf15ebc@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue maste r docker0 state UP group default link/ether 56:c6:04:4b:19:5f brd ff:ff:ff:ff:ff:ff link-netnsid 1 inet6 fe80::54c6:4ff:fe4b:195f/64 scope link valid_lft forever preferred_lft forever 14: veth041aaa8@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue maste r br-7d34e6c0f687 state UP group default link/ether fe:36:f9:f0:5e:e7 brd ff:ff:ff:ff:ff:ff link-netnsid 1 inet6 fe80::fc36:f9ff:fef0:5ee7/64 scope link valid_lft forever preferred_lft forever
相关文章推荐
- none 和 host 网络的适用场景 - 每天5分钟玩转 Docker 容器技术(31)
- none 和 host 网络的适用场景 - 每天5分钟玩转 Docker 容器技术(31)
- none 和 host 网络的适用场景 - 每天5分钟玩转 Docker 容器技术(31)
- none 和 host 网络的适用场景 - 每天5分钟玩转 Docker 容器技术(31)
- Docker网络之单host网络及使用案例
- Docker的none网络模式下创建一个点到点的连接(及4种docker网络模式)
- 17 - Docker network第三讲-自定义网络(Docker系列)
- Docker 配置网络 - 使用 host 网络
- Docker网络——单host网络
- docker - 由于docker swarm子网与host机器网络冲突导致的container通信问题的解决方案
- VMware、Docker虚拟机上网络连接(network type)的三种模式--bridged、host-only、NAT
- Docker none模式、DNS/HOSTNAME自定义、容器互联(网络三)
- centos7下安装docker(12.5容器在单个host上的网络总结)
- 利用pipework开源网络配置工具配置docker容器网络和host主机网络在同一个网段
- 『中级篇』容器网络之host和none(29)
- Docker系列教程17-默认bridge网络中配置DNS
- Docker网络——单host网络
- host网络模式(docker)下的端口映射
- docker的host、bridge网络类型
- 单机使用Docker host网络安装consul和registrator