docker network bridge模式,默认(一)

查看docker当前创建的网络

[root@localhost claroja]# docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
3c145f070fd7        bridge              bridge              local
f0428b4ac8ec        host                host                local
42c2aaaeac08        none                null                local

当创建容器时,默认都连接bridge局域网中,使用docker inspect bridge查看该模式的详细信息,containers为空,说明没有容器连接到此网络
缺点是不能通过DNS访问

[root@localhost claroja]# docker inspect bridge
[{"Name": "bridge","Id": "3c145f070fd74066ccdd08e447ebe511e698efa991842d14a5514233cb53ff72","Created": "2021-03-13T22:09:48.775941917-05:00","Scope": "local","Driver": "bridge","EnableIPv6": false,"IPAM": {"Driver": "default","Options": null,"Config": [{"Subnet": "172.17.0.0/16","Gateway": "172.17.0.1"}]},"Internal": false,"Attachable": false,"Ingress": false,"ConfigFrom": {"Network": ""},"ConfigOnly": false,"Containers": {},"Options": {"com.docker.network.bridge.default_bridge": "true","com.docker.network.bridge.enable_icc": "true","com.docker.network.bridge.enable_ip_masquerade": "true","com.docker.network.bridge.host_binding_ipv4": "0.0.0.0","com.docker.network.bridge.name": "docker0","com.docker.network.driver.mtu": "1500"},"Labels": {}}
]

创建容器test1

[root@localhost claroja]# docker container run --name test1 -dit centos /bin/bash
d0e15b7f6fd49f0d12d03edeffb8b6f844f722c97c78e7cba2ed4f7d8c8a89ed

创建容器test2

[root@localhost claroja]# docker container run --name test2 -dit centos /bin/bash
fb6ff2267a7f6f4e7fe31be9e8d016217459c74867d0529d5ed1867b6f76acc0

进入容器test1

[root@localhost claroja]# docker attach test1
[root@d0e15b7f6fd4 /]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft forever
12: eth0@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group defaultlink/ether 02:42:ac:11:00:03 brd ff:ff:ff:ff:ff:ff link-netnsid 0inet 172.17.0.2/16 brd 172.17.255.255 scope global eth0valid_lft forever preferred_lft forever

进入容器test2,ping test1的ip,可以ping通说明在同一个网段里

[root@localhost claroja]# docker attach test2
[root@fb6ff2267a7f /]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft forever
10: eth0@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group defaultlink/ether 02:42:ac:11:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0inet 172.17.0.3/16 brd 172.17.255.255 scope global eth0valid_lft forever preferred_lft forever[root@fb6ff2267a7f /]# ping 172.17.0.2
PING 172.17.0.2 (172.17.0.2) 56(84) bytes of data.
64 bytes from 172.17.0.2: icmp_seq=1 ttl=64 time=0.062 ms
64 bytes from 172.17.0.2: icmp_seq=2 ttl=64 time=0.051 ms

使用docker inspect bridge查看bridge模式下的状态,“Containers”,可查看当前容器的ip

[root@localhost claroja]# docker inspect bridge
[{"Name": "bridge","Id": "3c145f070fd74066ccdd08e447ebe511e698efa991842d14a5514233cb53ff72","Created": "2021-03-13T22:09:48.775941917-05:00","Scope": "local","Driver": "bridge","EnableIPv6": false,"IPAM": {"Driver": "default","Options": null,"Config": [{"Subnet": "172.17.0.0/16","Gateway": "172.17.0.1"}]},"Internal": false,"Attachable": false,"Ingress": false,"ConfigFrom": {"Network": ""},"ConfigOnly": false,"Containers": {"d0e15b7f6fd49f0d12d03edeffb8b6f844f722c97c78e7cba2ed4f7d8c8a89ed": {"Name": "test1","EndpointID": "da771a11c5fc38be893f5b8de85007cfe139c00d25f6cedc08a7d2051232d850","MacAddress": "02:42:ac:11:00:02","IPv4Address": "172.17.0.2/16","IPv6Address": ""},"fb6ff2267a7f6f4e7fe31be9e8d016217459c74867d0529d5ed1867b6f76acc0": {"Name": "test2","EndpointID": "d5bca6d5d219c132d5d93ed06fcc2330b23a7674391f1e04a4f1233d15e5db7d","MacAddress": "02:42:ac:11:00:03","IPv4Address": "172.17.0.3/16","IPv6Address": ""}},"Options": {"com.docker.network.bridge.default_bridge": "true","com.docker.network.bridge.enable_icc": "true","com.docker.network.bridge.enable_ip_masquerade": "true","com.docker.network.bridge.host_binding_ipv4": "0.0.0.0","com.docker.network.bridge.name": "docker0","com.docker.network.driver.mtu": "1500"},"Labels": {}}
]

参考:
https://blog.51cto.com/shyln/2133385

docker network bridge模式,默认(一)相关推荐

docker network bridge模式,自定义(一)
自定义bridge网络相比默认的bridge是可以使用容器名ping 创建自定义bridge网络 [root@localhost claroja]# docker network create --d ...
[Docker] docker network 常见模式及常用命令介绍
前言前端时间, 使用docker过程中, 又接触到需要docker network的相关知识. 之前的了解都是, 可以满足日常的使用即可, 本次, 借着机会仔细的了解了一下. 当然, 对于网络知识的 ...
docker network 网络模式
安装Docker时,自动创建3个网络模式(bridge,host,none),另外和可以自己指定一个(container): 网络名 bridge host none container模式不需要列出 ...
docker network host模式
宿主机在同一个网络中,但没有独立IP地址. Docker使用了Linux的Namespaces技术来进行资源隔离,如PID Namespace隔离进程,Mount Namespace隔离文件系统,Ne ...
Docker(十四)：Docker：网络模式详解
Docker作为目前最火的轻量级容器技术,牛逼的功能,如Docker的镜像管理,不足的地方网络方面. Docker自身的4种网络工作方式,和一些自定义网络模式安装Docker时,它会自动创建三个网络 ...
【Docker】网络模式
1.Host模式: Host 模式并没有为容器创建一个隔离的网络环境. 该模式下的Docker 容器会和Host宿主机共享同一个网络namespace, Docker Container可以和宿主机一 ...
查看此docker网络连接模式_Docker：网络模式详解
袖珍指南 Docker作为目前最火的轻量级容器技术,牛逼的功能,如Docker的镜像管理,不足的地方网络方面. Docker自身的4种网络工作方式,和一些自定义网络模式安装Docker时,它会自动创 ...
Docker：网络模式详解
http://www.cnblogs.com/zuxing/articles/8780661.html Docker:网络模式详解袖珍指南 Docker作为目前最火的轻量级容器技术,牛逼的功能,如D ...
查看此docker网络连接模式_Docker 网络模式（四种）详细介绍
Docker 网络模式本文首先介绍了Docker自身的4种网络工作方式, Docker作为目前最火的轻量级容器技术,有很多令人称道的功能,如Docker的镜像管理.然而,Docker同样有着很多不完 ...

docker network bridge模式,默认(一)

docker network bridge模式,默认(一)相关推荐

最新文章

热门文章