Shulou(Shulou.com)06/01 Report--

This article mainly introduces "what are the network basic knowledge points of Docker". In the daily operation, I believe that many people have doubts about the network basic knowledge points of Docker. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the questions of "what are the network basic knowledge points of Docker?" Next, please follow the editor to study!

The network

Docker provides several networks that determine what the container is and how the outside world communicates with the container.

You can view the network of docker in the following ways:

Docker network ls

Null: no network, containers using this kind of network will be completely isolated

Host: host network. Containers that use this network will use the host's network. This network is completely open to the outside world. If you can access the host, you can access the container.

Bridge: bridging network. Unless you specify a network when creating the container, the container uses the bridging network by default. Containers belonging to this network can communicate with each other, but if outsiders want to access containers of this network, they need to use a bridging network, which is a bit like a bridge between the host and the container, which can isolate the container to a certain extent.

Bridge network

View bridge network information:

Docker network inspect bridge

Information about the bridge network is listed, and containers indicates that the container of the network is used.

Create a container that uses the bridge network:

Docker run-d-name web1-net bridge nginxnone network

Create a container that uses the none network:

Docker run-d-- name web_none-- net none nginx

View none network information:

Docker network inspect nonehost network

Create a container that uses the host network:

Docker run-d-name web_host-net host nginx

You can see that the container does not have an IP address because it uses the host IP address directly

Port

If you want outsiders to have access to the services provided by containers created based on the bridge network, you must tell docker which port to use.

You can see which ports are used by the mirror in the following ways:

Docker inspect nginx | jq. []. "ContainerConfig". "ExposedPorts" port binding

When you create a container, you can specify the mapping between the container port and the host port:

Docker run-d-name web-p 8888purl 80 nginx

-pjinghewangis: you can specify the port relationship between the host and the container. On the left side of the colon is the port of the host, and on the right is the port mapped to the container.

-P: this parameter allocates all ports that will be used in the mirror and maps to random ports on the host

Check the port of the container:

Docker port web

If when creating a container, there is only one designated port after the-p parameter, which means that the host randomly maps to the designated port of the container:

Docker run-d-name web-p 80 nginx custom network

Custom networks can be created based on a certain type of network, so that containers belonging to that network can be isolated, they can communicate with each other, and containers that are not in this network cannot directly access them. A container can belong to multiple networks, and containers under the same custom network can access each other through their respective container names, because a dns feature embedded in docker is used.

Create a custom network:

Docker network create-- driver bridge custom #-- driver is used to specify the network type

You can view the information about the newly created custom network through docker network ls. Subnet represents the IP segment of the subnet under this network, then the container IP created based on the custom custom network will start with this IP segment.

Create a container based on the custom network:

Docker run-d-- name web2-- net custom nginx

If you want to put the container you have created into a custom network, use the following directive:

Docker network connect custom web

Remove web from the bridge network:

Docker network disconnect bridge web at this point, about "what are the basic network knowledge points of Docker," the study is over, I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.