CN106067858A - Communication means between container, Apparatus and system - Google Patents
Communication means between container, Apparatus and system Download PDFInfo
- Publication number
- CN106067858A CN106067858A CN201610350477.1A CN201610350477A CN106067858A CN 106067858 A CN106067858 A CN 106067858A CN 201610350477 A CN201610350477 A CN 201610350477A CN 106067858 A CN106067858 A CN 106067858A
- Authority
- CN
- China
- Prior art keywords
- container
- address
- virtual bridge
- public network
- private net
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
- H04L12/462—LAN interconnection over a bridge based backbone
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
Abstract
The embodiment of the present invention provides the communication means between a kind of container, Apparatus and system.The method includes: the first virtual bridge sends Address requests message to coordinating network element；First virtual bridge receives the public network address coordinating the target container that network element sends；First virtual bridge according to the public network address of target container to the message of the second virtual bridge transmission source container.The embodiment of the present invention creates virtual bridge by different Docker servers, virtual bridge is the container allocation private net address on the Docker server at its place, it is dispersed in the container of same user on different Docker server and is obtained IP address and the port numbers of communication counterpart container place Docker server by virtual bridge from coordination network element, the IP address of cubitainer place Docker server is communicated with to cubitainer by foundation with port numbers, it is achieved that be dispersed in the communication between the container of same user on different Docker server in three-layer network.
Description
Technical field
The present embodiments relate to communication technical field, particularly relate to the communication means between a kind of container, Apparatus and system.
Background technology
Docker is an application container engine increased income, after physical host installs Docker, and can be Docker's
On the basis of carry multiple container, mutually isolated between multiple containers, multiple containers share the operating system of physical host, each container
Can place and perform different application programs.
In prior art, it is dispersed in three-layer network on different Docker server and belongs between the container of same user
Cannot proper communication.
Summary of the invention
The embodiment of the present invention provides the communication means between a kind of container, Apparatus and system, to realize being dispersed in three-layer network
On middle different Docker server and belong to the proper communication between the container of same user.
One aspect of the embodiment of the present invention is to provide the communication means between a kind of container, including:
First virtual bridge sends Address requests message to coordinating network element, and described Address requests message includes target container
Private net address, so that described coordination network element obtains the public network ground of described target container according to the private net address of described target container
Location；
Described first virtual bridge receives the public network address of the described target container that described coordination network element sends；
Described first virtual bridge according to the public network address of described target container to the second virtual bridge transmission source container
Message, so that described message is sent to described target container by described second virtual bridge；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual net
Bridge and described target container are positioned at the 2nd Docker server.
Another aspect of the embodiment of the present invention is to provide the communication means between a kind of container, including:
Coordinating network element and receive the Address requests message that the first virtual bridge sends, described Address requests message includes that target is held
The private net address of device；
Described coordination network element obtains the public network address of described target container according to the private net address of described target container；
Described coordination network element sends the public network address of described target container to described first virtual bridge, so that described first
Virtual bridge according to the public network address of described target container to the message of the second virtual bridge transmission source container so that described second
Described message is sent to described target container by virtual bridge；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual net
Bridge and described target container are positioned at the 2nd Docker server.
Another aspect of the embodiment of the present invention is to provide a kind of virtual bridge, including:
Sending module, for coordinating network element transmission Address requests message, described Address requests message includes target container
Private net address so that described coordination network element according to described target container private net address obtain described target container public network ground
Location；
Receiver module, for receiving the public network address of the described target container that described coordination network element sends；
Described sending module is additionally operable to the public network address according to described target container to other virtual bridge transmission source containers
Message so that described message is sent to described target container by other virtual bridges described；
Wherein, described virtual bridge and described source container are positioned at a Docker server, other virtual bridges described and
Described target container is positioned at the 2nd Docker server.
Another aspect of the embodiment of the present invention is to provide a kind of coordination network element, including:
Receiver module, for receiving the Address requests message that the first virtual bridge sends, described Address requests message includes
The private net address of target container；
Acquisition module, for obtaining the public network address of described target container according to the private net address of described target container；
Sending module, for sending the public network address of described target container to described first virtual bridge, so that described the
One virtual bridge according to the public network address of described target container to the message of the second virtual bridge transmission source container so that described
Described message is sent to described target container by two virtual bridges；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual net
Bridge and described target container are positioned at the 2nd Docker server.
Another aspect of the embodiment of the present invention is to provide the communication system between a kind of container, including described virtual bridge
With described coordination network element.
Communication means between the container that the embodiment of the present invention provides, Apparatus and system, by servicing at different Docker
Device creates virtual bridge, and virtual bridge is the container allocation private net address on the Docker server at its place, is dispersed in difference
On Docker server, the container of same user obtains communication counterpart container place by virtual bridge from coordinating network element
The IP address of Docker server and port numbers, according to the IP address of cubitainer place Docker server and port numbers with right
Cubitainer communicates, it is achieved that be dispersed in leading between the container of same user on different Docker server in three-layer network
Letter.
Accompanying drawing explanation
Fig. 1 is Docker server and the connection diagram of subnet in prior art；
Fig. 2 is Docker server and the connection diagram of subnet in prior art；
Communication means flow chart between the container that Fig. 3 provides for the embodiment of the present invention；
The network architecture diagram that communication means between the container that Fig. 4 provides for the embodiment of the present invention is suitable for；
Communication means flow chart between the container that Fig. 5 provides for another embodiment of the present invention；
Communication means flow chart between the container that Fig. 6 provides for another embodiment of the present invention；
Communication means flow chart between the container that Fig. 7 provides for another embodiment of the present invention；
The structure chart of the virtual bridge that Fig. 8 provides for the embodiment of the present invention；
The structure chart of the virtual bridge that Fig. 9 provides for another embodiment of the present invention；
The structure chart coordinating network element that Figure 10 provides for the embodiment of the present invention；
The structure chart coordinating network element that Figure 11 provides for another embodiment of the present invention；
The structure chart of the communication system between the container that Figure 12 provides for the embodiment of the present invention.
Detailed description of the invention
Fig. 1 is Docker server and the connection diagram of subnet in prior art.As it is shown in figure 1, Docker server
21 belong to subnet 20, and Docker server 21 includes container 31 and container 32, are provided with Microsoft Loopback Adapter 41, in container 32 in container 31
It is provided with Microsoft Loopback Adapter 42, Microsoft Loopback Adapter 41 and Microsoft Loopback Adapter 42 to be connected with bridge 43 respectively, bridge 43 and Docker server 21
Physical network card 44 connect.Bridge 43 respectively container 31 and container 32 distribute mutually different private net address, when container 31 or
During equipment outside container 32 access subnetwork 20, container 31 or container 32 send message to bridge 43, and message includes private net address,
Private net address is converted to the public network address of Docker server 21 and is sent by message by bridge 43.It addition, container 31 and appearance
The different port of the most corresponding Docker server 21 of device 32, the equipment outside subnet 20 is according to the public network of Docker server 21
Address and the port numbers of container this port numbers is corresponding on Docker server 21 container can send message.
Fig. 2 is Docker server and the connection diagram of subnet in prior art.As in figure 2 it is shown, on the basis of Fig. 1
On, Docker server 21 and Docker server 51 belongs to three-layer network 30, and Docker server 51 includes container 61 He
Container 62, is provided with Microsoft Loopback Adapter 71 in container 61, be provided with Microsoft Loopback Adapter 72, Microsoft Loopback Adapter 71 and Microsoft Loopback Adapter 72 points in container 62
Not being connected with bridge 73, bridge 73 is connected with the physical network card 74 of Docker server 51.Assume that container 31 and container 61 belong to
User A, container 32 and container 62 belong to user B, and the container of the most same user is dispersed on different Docker servers.
Communication means flow chart between the container that Fig. 3 provides for the embodiment of the present invention；Fig. 4 provides for the embodiment of the present invention
The network architecture diagram that communication means between container is suitable for.The embodiment of the present invention, in prior art, is dispersed in three-layer network
On different Docker servers and belong between the container of same user cannot proper communication, it is provided that the communication party between container
Method, the method specifically comprises the following steps that
Step S101, the first virtual bridge send Address requests message to coordinating network element, and described Address requests message includes
The private net address of target container, so that described coordination network element obtains described target container according to the private net address of described target container
Public network address；
Embodiments provide between the container belonging to same user being dispersed on different Docker servers
Communication means, the communication means between container 31 and container 61 the most as shown in Figure 2, between container 32 and container 62, this
Bright embodiment is introduced as a example by the communication means between container 31 and container 61.
As shown in Figure 4, Docker server 21 creates proxy module 83, creates first by proxy module 83 virtual
Bridge 81, proxy module 83 is connected with the first virtual bridge 81, and proxy module 83 is for by three-layer network 30 and coordination network element
10 communications, the first virtual bridge 81 communicates with container 31.Docker server 51 creates proxy module 84, by acting on behalf of mould
Block 84 creates the second virtual bridge 82, and proxy module 84 and the second virtual bridge 82 connect, and proxy module 84 passes through three-layer network
30 communicate with coordinating network element 10, and the second virtual bridge 82 communicates with container 61.Coordinate network element 10 and be also associated with managed network element 11, the
One virtual bridge 81 sends existing state and the resources occupation rate of container 31 by proxy module 83 to coordination network element 10, coordinates net
Unit 10 sends existing state and the resources occupation rate of container 31 to managed network element 11, in order to managed network element 11 real time record container 31
Existing state and resources occupation rate, in like manner, managed network element 11 can also record existing state and the resource occupation of other containers
Rate.
It addition, after container 31 and container 61 are closed, delete the first virtual bridge 81 by proxy module 83, by agency
Module 84 deletes the second virtual bridge 82.
In embodiments of the present invention, coordinate network element 10 and determine the private net address that each Docker server upper container can be allocated
Scope, such as, the scope coordinating the private net address that network element 10 determines that the container on Docker server 21 can be allocated is
192.168.0.100-199, the scope of the private net address that the container on Docker server 51 can be allocated is
192.168.0.200-254, coordinate network element 10 and network segment 192.168.0.100-199 be sent to the agency of Docker server 21
Module 83, and network segment 192.168.0.200-254 is sent to the proxy module 84 of Docker server 51；Proxy module 83 will
Network segment 192.168.0.100-199 is sent to the first virtual bridge 81, and network segment 192.168.0.200-254 is sent out by proxy module 84
Give the second virtual bridge 82；First virtual bridge 81 distributes private net address 192.168.0.100 for container 31, the second virtual net
Bridge 82 distributes private net address 192.168.0.200 for container 61.
In embodiments of the present invention, the first virtual bridge 81 is by the identification information of container 31 and the private net address of container 31
192.168.0.100 being sent to user terminal, the second virtual bridge 82 is by the private network ground of the identification information of container 61 and container 61
Location 192.168.0.200 is sent to user terminal, and when container 31 needs to communicate with container 61, user terminal is by the private of container 61
Net address 192.168.0.200 is sent to container 31, and the private net address 192.168.0.100 of container 31 is sent to container
61.Container 31 generates the first message, and the first message includes private network source address and private network destination address, specifically, private network source address
Being the private net address 192.168.0.100 of container 31, private network destination address is the private net address 192.168.0.200 of container 61.
This first message is sent to the first virtual bridge 81 by container 31, and the first virtual bridge 81 generates address according to this first message please
Seeking message, this Address requests message includes the target container i.e. private net address 192.168.0.200 of container 61, and please by this address
Ask message to pass through proxy module 83 to be sent to coordinate network element 10, coordinate network element 10 maintains have Database Lists, this database column
The identification information of each container of each Docker server that table includes being connected with three-layer network 30, the i.e. user of the owner of container
Identification information, the private net address of container, the IP address of Docker server at container place, container take Docker server
Port numbers, the identification information of proxy module, the IP address of Docker server at proxy module place.
Coordinate the Address requests message that sends according to proxy module 83 of network element 10, determine proxy module 83 identification information,
The IP address such as 202.x.x.1 of the IP address i.e. Docker server 21 of the Docker server at proxy module 83 place, association
Adjust network element 10 to obtain the target container in the Address requests message i.e. private net address 192.168.0.200 of container 61, coordinate network element
10 inquire about Database Lists according to the private net address 192.168.0.200 of container 61, it is thus achieved that the Docker service at container 61 place
The IP address such as 202.x.x.2 of the IP address i.e. Docker server 51 of device and container 61 take the end of Docker server 51
Slogan such as 5678, coordinate network element 10 by the IP address 202.x.x.2 of the Docker server at container 61 place determined and
Container 61 takies the port numbers 5678 of Docker server and is sent to proxy module 83.
Step S102, described first virtual bridge receive the public network ground of the described target container that described coordination network element sends
Location.
IP address 202.x.x.2 and the container 61 of the Docker server at container 61 place are taken by proxy module 83
The port numbers 5678 of Docker server is sent to the first virtual bridge 81.
Step S103, described first virtual bridge send to the second virtual bridge according to the public network address of described target container
The message of source container, so that described message is sent to described target container by described second virtual bridge；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual net
Bridge and described target container are positioned at the 2nd Docker server.
First virtual bridge 81 receives IP address 202.x.x.2 and the container 61 of the Docker server at container 61 place
After taking the port numbers 5678 of Docker server, according to the IP address 202.x.x.2 of the Docker server at container 61 place
The first message take the port numbers 5678 of Docker server with container 61 after sent container 31 carries out Reseal, again
The form of the first message after encapsulation is as shown in table 1:
Table 1
As shown in Table 1, container 31 by the first virtual bridge 81 to the first message that container 61 sends include heading and
Message text, heading includes public network source address and public network destination address, public network source address be container 31 public network IP address and
Port numbers i.e. 202.x.x.1:1234, public network destination address is public network IP address and the port numbers i.e. 202.x.x.2 of container 61:
5678, message text includes private network source address, private network destination address and message content, and private network source address is the private network IP of container 31
Address i.e. 192.168.0.100, private network destination address is the private network IP address i.e. 192.168.0.200 of container 61.
The embodiment of the present invention is by creating virtual bridge at different Docker servers, and virtual bridge is its place
Container allocation private net address on Docker server, is dispersed in the container of same user on different Docker server and passes through
Virtual bridge obtains IP address and the port numbers of communication counterpart container place Docker server from coordinating network element, holds according to the other side
The IP address of device place Docker server communicates with to cubitainer with port numbers, it is achieved that be dispersed in difference in three-layer network
Communication between the container of same user on Docker server.
Communication means flow chart between the container that Fig. 5 provides for another embodiment of the present invention；In embodiment corresponding for Fig. 3
On the basis of, specifically comprising the following steps that of the communication means between the container that the embodiment of the present invention provides
Step S501, the first virtual bridge distribute private net address to described source container；
In the above-described embodiments, the private net address that network element 10 determines that each Docker server upper container can be allocated is coordinated
Scope, such as, the scope coordinating the private net address that network element 10 determines that the container on Docker server 21 can be allocated is
192.168.0.100-199, the scope of the private net address that the container on Docker server 51 can be allocated is
192.168.0.200-254, coordinate network element 10 and network segment 192.168.0.100-199 be sent to the agency of Docker server 21
Module 83, and network segment 192.168.0.200-254 is sent to the proxy module 84 of Docker server 51；Proxy module 83 will
Network segment 192.168.0.100-199 is sent to the first virtual bridge 81, and network segment 192.168.0.200-254 is sent out by proxy module 84
Give the second virtual bridge 82；First virtual bridge 81 distributes private net address 192.168.0.100 for container 31, the second virtual net
Bridge 82 distributes private net address 192.168.0.200 for container 61.In the embodiment of the present invention, source container is container 31, target container
It it is container 61.
Step S502, described first virtual bridge send the private net address of described source container and described to described coordination network element
The public network address of source container, the public network address of described source container includes that public network IP address and port numbers, described public network IP address are
The IP address of a described Docker server；
After first virtual bridge 81 distributes private net address 192.168.0.100 for container 31, the first virtual bridge 81 is to association
Adjust network element 10 send the private net address 192.168.0.100 of container 31 and container 31 public network address, specifically, container 31
Public network address includes public network IP address and the port numbers of container 31, and the public network IP address of container 31 is the IP of Docker server 21
Address such as 202.x.x.1, port numbers is the port numbers such as 1234 that container 31 takies on Docker server 21.Coordinate net
The private net address 192.168.0.100 of container 31, the public network IP address 202.x.x.1 of container 31, port numbers 1234 are deposited by unit 10
Storage is at Database Lists.
In like manner, after the second virtual bridge 82 distributes private net address 192.168.0.200 for container 61, the second virtual bridge 82
Private net address 192.168.0.200 and the public network address of container 61 of container 61, specifically, container 61 is sent to coordination network element 10
Public network address include public network IP address and the port numbers of container 61, the public network IP address of container 61 is Docker server 51
IP address such as 202.x.x.2, port numbers is the port numbers such as 5678 that container 61 takies on Docker server 51.Coordinate
Network element 10 is by the private net address 192.168.0.200 of container 61, the public network IP address 202.x.x.2 of container 61 and port numbers 5678
It is stored in Database Lists.
The relevant information of the container on other Docker servers being connected with three-layer network 30 is in Database Lists
Creation method identical with the relevant information of container 31 and container 61 creation method in Database Lists.
Step S503, the first virtual bridge send Address requests message to coordinating network element, and described Address requests message includes
The private net address of target container, so that described coordination network element obtains described target container according to the private net address of described target container
Public network address；
Described Address requests message also includes the private net address of described source container.In embodiments of the present invention, first is virtual
Bridge 81 includes the private network ground of the i.e. container 31 of private net address of source container to the Address requests message coordinating network element 10 transmission simultaneously
The public network address of location and the target container i.e. public network address of container 61.
Step S504, described first virtual bridge receive the public network ground of the described target container that described coordination network element sends
Location；
Step S505, described first virtual bridge send to the second virtual bridge according to the public network address of described target container
The message of source container, so that described message is sent to described target container by described second virtual bridge；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual net
Bridge and described target container are positioned at the 2nd Docker server.
The embodiment of the present invention distributes private net address by the first virtual bridge to source container, and the first virtual bridge is to coordinating net
The private net address of unit's transmission source container and the public network address of source container, coordinate network element and store the private of source container in Database Lists
Net address and the public network address of source container, it is ensured that target container can inquire about the public network ground getting source container by coordination network element
Location, it is achieved that source container communicates with target container.
Communication means flow chart between the container that Fig. 6 provides for another embodiment of the present invention；The embodiment of the present invention provides
Specifically comprising the following steps that of communication means between container
Step S601, coordination network element receive the Address requests message that the first virtual bridge sends, described Address requests message
Private net address including target container；
As shown in Figure 4, Docker server 21 creates proxy module 83, creates first by proxy module 83 virtual
Bridge 81, proxy module 83 is connected with the first virtual bridge 81, and proxy module 83 is for by three-layer network 30 and coordination network element
10 communications, the first virtual bridge 81 communicates with container 31.Docker server 51 creates proxy module 84, by acting on behalf of mould
Block 84 creates the second virtual bridge 82, and proxy module 84 and the second virtual bridge 82 connect, and proxy module 84 passes through three-layer network
30 communicate with coordinating network element 10, and the second virtual bridge 82 communicates with container 61.
In embodiments of the present invention, coordinate network element 10 and determine the private net address that each Docker server upper container can be allocated
Scope, such as, the scope coordinating the private net address that network element 10 determines that the container on Docker server 21 can be allocated is
192.168.0.100-199, the scope of the private net address that the container on Docker server 51 can be allocated is
192.168.0.200-254, coordinate network element 10 and network segment 192.168.0.100-199 be sent to the agency of Docker server 21
Module 83, and network segment 192.168.0.200-254 is sent to the proxy module 84 of Docker server 51；Proxy module 83 will
Network segment 192.168.0.100-199 is sent to the first virtual bridge 81, and network segment 192.168.0.200-254 is sent out by proxy module 84
Give the second virtual bridge 82；First virtual bridge 81 distributes private net address 192.168.0.100 for container 31, the second virtual net
Bridge 82 distributes private net address 192.168.0.200 for container 61.
In embodiments of the present invention, the first virtual bridge 81 is by the identification information of container 31 and the private net address of container 31
192.168.0.100 being sent to user terminal, the second virtual bridge 82 is by the private network ground of the identification information of container 61 and container 61
Location 192.168.0.200 is sent to user terminal, and when container 31 needs to communicate with container 61, user terminal is by the private of container 61
Net address 192.168.0.200 is sent to container 31, and the private net address 192.168.0.100 of container 31 is sent to container
61.Container 31 generates the first message, and the first message includes private network source address and private network destination address, specifically, private network source address
Being the private net address 192.168.0.100 of container 31, private network destination address is the private net address 192.168.0.200 of container 61.
This first message is sent to the first virtual bridge 81 by container 31, and the first virtual bridge 81 generates address according to this first message please
Seeking message, this Address requests message includes the target container i.e. private net address 192.168.0.200 of container 61, and please by this address
Ask message to pass through proxy module 83 to be sent to coordinate network element 10, coordinate network element 10 maintains have Database Lists, this database column
The identification information of each container of each Docker server that table includes being connected with three-layer network 30, the i.e. user of the owner of container
Identification information, the private net address of container, the IP address of Docker server at container place, container take Docker server
Port numbers, the identification information of proxy module, the IP address of Docker server at proxy module place.
Coordinate the Address requests message that sends according to proxy module 83 of network element 10, determine proxy module 83 identification information,
The IP address such as 202.x.x.1 of the IP address i.e. Docker server 21 of the Docker server at proxy module 83 place.
Step S602, described coordination network element obtain the public network of described target container according to the private net address of described target container
Address；
Coordinate network element 10 and obtain the target container in the Address requests message i.e. private net address of container 61
192.168.0.200, coordinate network element 10 and inquire about Database Lists according to the private net address 192.168.0.200 of container 61, it is thus achieved that
The IP address such as 202.x.x.2 of the IP address i.e. Docker server 51 of the Docker server at container 61 place and container 61
Take the port numbers such as 5678 of Docker server 51, coordinate network element 10 and the Docker at container 61 place determined is serviced
The IP address 202.x.x.2 of device and container 61 take the port numbers 5678 of Docker server and are sent to proxy module 83.
Step S603, described coordination network element send the public network address of described target container to described first virtual bridge, with
Make described first virtual bridge according to the public network address of described target container to the message of the second virtual bridge transmission source container, with
Make described second virtual bridge that described message is sent to described target container；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual net
Bridge and described target container are positioned at the 2nd Docker server；
IP address 202.x.x.2 and the container 61 of the Docker server at container 61 place are taken by proxy module 83
The port numbers 5678 of Docker server is sent to the first virtual bridge 81.
First virtual bridge 81 receives IP address 202.x.x.2 and the container 61 of the Docker server at container 61 place
After taking the port numbers 5678 of Docker server, according to the IP address 202.x.x.2 of the Docker server at container 61 place
The first message take the port numbers 5678 of Docker server with container 61 after sent container 31 carries out Reseal, again
The form of the first message after encapsulation is as shown in table 1:
Table 1
As shown in Table 1, container 31 by the first virtual bridge 81 to the first message that container 61 sends include heading and
Message text, heading includes public network source address and public network destination address, public network source address be container 31 public network IP address and
Port numbers i.e. 202.x.x.1:1234, public network destination address is public network IP address and the port numbers i.e. 202.x.x.2 of container 61:
5678, message text includes private network source address, private network destination address and message content, and private network source address is the private network IP of container 31
Address i.e. 192.168.0.100, private network destination address is the private network IP address i.e. 192.168.0.200 of container 61.
The embodiment of the present invention is by creating virtual bridge at different Docker servers, and virtual bridge is its place
Container allocation private net address on Docker server, is dispersed in the container of same user on different Docker server and passes through
Virtual bridge obtains IP address and the port numbers of communication counterpart container place Docker server from coordinating network element, holds according to the other side
The IP address of device place Docker server communicates with to cubitainer with port numbers, it is achieved that be dispersed in difference in three-layer network
Communication between the container of same user on Docker server.
Communication means flow chart between the container that Fig. 7 provides for another embodiment of the present invention；In embodiment corresponding for Fig. 6
On the basis of, specifically comprising the following steps that of the communication means between the container that the embodiment of the present invention provides
Step S701, described coordination network element receive described first virtual bridge send described source container private net address and
The public network address of described source container, the private net address of described source container is that described first virtual bridge distributes to described source container
Private net address；The public network address of described source container includes that public network IP address and port numbers, described public network IP address are described first
The IP address of Docker server；
In the above-described embodiments, the private net address that network element 10 determines that each Docker server upper container can be allocated is coordinated
Scope, such as, the scope coordinating the private net address that network element 10 determines that the container on Docker server 21 can be allocated is
192.168.0.100-199, the scope of the private net address that the container on Docker server 51 can be allocated is
192.168.0.200-254, coordinate network element 10 and network segment 192.168.0.100-199 be sent to the agency of Docker server 21
Module 83, and network segment 192.168.0.200-254 is sent to the proxy module 84 of Docker server 51；Proxy module 83 will
Network segment 192.168.0.100-199 is sent to the first virtual bridge 81, and network segment 192.168.0.200-254 is sent out by proxy module 84
Give the second virtual bridge 82；First virtual bridge 81 distributes private net address 192.168.0.100 for container 31, the second virtual net
Bridge 82 distributes private net address 192.168.0.200 for container 61.In the embodiment of the present invention, source container is container 31, target container
It it is container 61.
After first virtual bridge 81 distributes private net address 192.168.0.100 for container 31, the first virtual bridge 81 is to association
Adjust network element 10 send the private net address 192.168.0.100 of container 31 and container 31 public network address, specifically, container 31
Public network address includes public network IP address and the port numbers of container 31, and the public network IP address of container 31 is the IP of Docker server 21
Address such as 202.x.x.1, port numbers is the port numbers such as 1234 that container 31 takies on Docker server 21.
In like manner, after the second virtual bridge 82 distributes private net address 192.168.0.200 for container 61, the second virtual bridge 82
Private net address 192.168.0.200 and the public network address of container 61 of container 61, specifically, container 61 is sent to coordination network element 10
Public network address include public network IP address and the port numbers of container 61, the public network IP address of container 61 is Docker server 51
IP address such as 202.x.x.2, port numbers is the port numbers such as 5678 that container 61 takies on Docker server 51.
The private net address of described source container and the public network address of described source container are stored by step S702, described coordination network element
At Database Lists；
Coordinate network element 10 by the private net address 192.168.0.100 of container 31, the public network IP address of container 31
202.x.x.1, port numbers 1234 are stored in Database Lists.
Coordinate network element 10 by the private net address 192.168.0.200 of container 61, the public network IP address 202.x.x.2 of container 61
It is stored in Database Lists with port numbers 5678.
The relevant information of the container on other Docker servers being connected with three-layer network 30 is in Database Lists
Creation method identical with the relevant information of container 31 and container 61 creation method in Database Lists.
Step S703, coordination network element receive the Address requests message that the first virtual bridge sends, described Address requests message
Private net address including target container；
Described Address requests message also includes the private net address of described source container.In embodiments of the present invention, first is virtual
Bridge 81 includes the private network ground of the i.e. container 31 of private net address of source container to the Address requests message coordinating network element 10 transmission simultaneously
The public network address of location and the target container i.e. public network address of container 61.
Step S704, described coordination network element inquire about Database Lists, described number according to the private net address of described target container
Private net address and the public network address of described default container presetting container is included according to storehouse list；
Coordinating to maintain in network element 10 have Database Lists, this Database Lists includes each with what three-layer network 30 was connected
The identification information of each container of Docker server, the owner i.e. identification information of user of container, the private net address of container, appearance
The IP address of the Docker server at device place, container take the port numbers of Docker server, the identification information of proxy module,
The IP address of the Docker server at proxy module place.Specifically, Database Lists includes the relevant letter of multiple default container
Cease, and relevant information includes private net address and the public network address of this container.Coordinate network element 10 according to the identification information of container 61, appearance
The identification information of the user of device 61, the private net address 192.168.0.200 of container 61 inquire about Database Lists.
If the default container that the described Database Lists of step S705 includes mating with the private net address of described target container
Private net address, the public network address that the most described coordination network element determines described target container is the public network address of described default container；
If described Database Lists includes the private of the default container that the private net address 192.168.0.200 with container 61 mates
Net address, represents that Database Lists includes the private net address 192.168.0.200 of container 61, then coordinates network element 10 from data base
List obtains the public network address of container 61.
Step S706, described coordination network element send the public network address of described target container to described first virtual bridge, with
Make described first virtual bridge according to the public network address of described target container to the message of the second virtual bridge transmission source container, with
Make described second virtual bridge that described message is sent to described target container；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual net
Bridge and described target container are positioned at the 2nd Docker server.
The embodiment of the present invention distributes private net address by the first virtual bridge to source container, and the first virtual bridge is to coordinating net
The private net address of unit's transmission source container and the public network address of source container, coordinate network element and store the private of source container in Database Lists
Net address and the public network address of source container, it is ensured that target container can inquire about the public network ground getting source container by coordination network element
Location, it is achieved that source container communicates with target container.
The structure chart of the virtual bridge that Fig. 8 provides for the embodiment of the present invention.The virtual bridge that the embodiment of the present invention provides can
To perform the handling process that the communication means embodiment between container provides, as shown in Figure 8, virtual bridge 80 includes sending module 81
With receiver module 82, wherein, sending module 81 is for coordinating network element transmission Address requests message, described Address requests message bag
Include the private net address of target container, hold so that described coordination network element obtains described target according to the private net address of described target container
The public network address of device；Receiver module 82 is for receiving the public network address of the described target container that described coordination network element sends；Described
Sending module 81 is additionally operable to the message to other virtual bridge transmission source containers of the public network address according to described target container, so that
Described message is sent to described target container by other virtual bridges described；Wherein, described virtual bridge and described source container position
In a Docker server, other virtual bridges described and described target container are positioned at the 2nd Docker server.
The embodiment of the method that the virtual bridge that the embodiment of the present invention provides can be provided specifically for the above-mentioned Fig. 3 of execution,
Here is omitted for concrete function
The embodiment of the present invention is by creating virtual bridge at different Docker servers, and virtual bridge is its place
Container allocation private net address on Docker server, is dispersed in the container of same user on different Docker server and passes through
Virtual bridge obtains IP address and the port numbers of communication counterpart container place Docker server from coordinating network element, holds according to the other side
The IP address of device place Docker server communicates with to cubitainer with port numbers, it is achieved that be dispersed in difference in three-layer network
Communication between the container of same user on Docker server.
The structure chart of the virtual bridge that Fig. 9 provides for another embodiment of the present invention.On the basis of above-described embodiment, virtual
Bridge 80 also includes distributing module 83, and distribution module 83 is for distributing private net address to described source container；Sending module 81 is also used
In the private net address from described source container to described coordination network element and the public network address of described source container, the public affairs of described source container that send
Net address includes that public network IP address and port numbers, described public network IP address are the IP addresses of a described Docker server.
The embodiment of the method that the virtual bridge that the embodiment of the present invention provides can be provided specifically for the above-mentioned Fig. 5 of execution,
Here is omitted for concrete function.
The embodiment of the present invention distributes private net address by the first virtual bridge to source container, and the first virtual bridge is to coordinating net
The private net address of unit's transmission source container and the public network address of source container, coordinate network element and store the private of source container in Database Lists
Net address and the public network address of source container, it is ensured that target container can inquire about the public network ground getting source container by coordination network element
Location, it is achieved that source container communicates with target container.
The structure chart coordinating network element that Figure 10 provides for the embodiment of the present invention.The coordination network element that the embodiment of the present invention provides can
To perform the handling process that the communication means embodiment between container provides, as shown in Figure 10, coordinate network element 100 and include receiver module
101, acquisition module 102 and sending module 103, wherein, the address that receiver module 101 sends for receiving the first virtual bridge please
Message, described Address requests message is asked to include the private net address of target container；Acquisition module 102 is for according to described target container
Private net address obtain described target container public network address；Sending module 103 is for sending institute to described first virtual bridge
State the public network address of target container, so that described first virtual bridge is virtual to second according to the public network address of described target container
The message of bridge transmission source container, so that described message is sent to described target container by described second virtual bridge；Wherein, institute
State the first virtual bridge and described source container is positioned at a Docker server, described second virtual bridge and described target container
It is positioned at the 2nd Docker server.
What the embodiment of the present invention provided coordinates the embodiment of the method that network element can be provided specifically for the above-mentioned Fig. 6 of execution,
Here is omitted for concrete function.
The embodiment of the present invention is by creating virtual bridge at different Docker servers, and virtual bridge is its place
Container allocation private net address on Docker server, is dispersed in the container of same user on different Docker server and passes through
Virtual bridge obtains IP address and the port numbers of communication counterpart container place Docker server from coordinating network element, holds according to the other side
The IP address of device place Docker server communicates with to cubitainer with port numbers, it is achieved that be dispersed in difference in three-layer network
Communication between the container of same user on Docker server.
The structure chart coordinating network element that Figure 11 provides for another embodiment of the present invention.On the basis of above-described embodiment, obtain
Delivery block 102 includes query unit 1021 and determines unit 1022, and wherein, query unit 1021 is for according to described target container
Private net address inquiry Database Lists, described Database Lists includes presetting the private net address of container and described default container
Public network address；If it is pre-with what the private net address of described target container mated to determine that unit 1022 includes for described Database Lists
If the private net address of container, it is determined that the public network address of described target container is the public network address of described default container.
Described receiver module 101 be additionally operable to receive the described source container that described first virtual bridge sends private net address and
The public network address of described source container, the private net address of described source container is that described first virtual bridge distributes to described source container
Private net address；The public network address of described source container includes that public network IP address and port numbers, described public network IP address are described first
The IP address of Docker server；
Described coordination network element 100 also includes memory module 104, and memory module 104 is for by the private network ground of described source container
The public network address of location and described source container is stored in Database Lists.
What the embodiment of the present invention provided coordinates the embodiment of the method that network element can be provided specifically for the above-mentioned Fig. 7 of execution,
Here is omitted for concrete function.
The embodiment of the present invention distributes private net address by the first virtual bridge to source container, and the first virtual bridge is to coordinating net
The private net address of unit's transmission source container and the public network address of source container, coordinate network element and store the private of source container in Database Lists
Net address and the public network address of source container, it is ensured that target container can inquire about the public network ground getting source container by coordination network element
Location, it is achieved that source container communicates with target container.
The structure chart of the communication system between the container that Figure 12 provides for the embodiment of the present invention.The appearance that the embodiment of the present invention provides
Communication system between device can perform the handling process that the communication means embodiment between container provides, as shown in figure 12, between container
Communication system 120 include the virtual bridge 80 in above-described embodiment and the coordination network element 100 in above-described embodiment.
Communication system between the container that the embodiment of the present invention provides can perform the communication means embodiment between container to be provided
Handling process.
In sum, the embodiment of the present invention is by creating virtual bridge at different Docker servers, and virtual bridge is
Container allocation private net address on the Docker server at its place, is dispersed in same user on different Docker server
Container obtains IP address and the port numbers of communication counterpart container place Docker server by virtual bridge from coordination network element, depends on
Communicate with to cubitainer with port numbers according to the IP address of cubitainer place Docker server, it is achieved that in three-layer network point
It is dispersed in the communication between the container of same user on different Docker server；Distributed to source container by the first virtual bridge
Private net address, the first virtual bridge, to coordinating the private net address of network element transmission source container and the public network address of source container, coordinates net
Unit stores the private net address of source container and the public network address of source container in Database Lists, it is ensured that target container is by coordinating net
The public network address getting source container can be inquired about by unit, it is achieved that source container communicates with target container.
In several embodiments provided by the present invention, it should be understood that disclosed apparatus and method, can be passed through it
Its mode realizes.Such as, device embodiment described above is only schematically, such as, and the division of described unit, only
Being only a kind of logic function to divide, actual can have other dividing mode, the most multiple unit or assembly to tie when realizing
Close or be desirably integrated into another system, or some features can be ignored, or not performing.Another point, shown or discussed
Coupling each other or direct-coupling or communication connection can be the INDIRECT COUPLING by some interfaces, device or unit or logical
Letter connects, and can be electrical, machinery or other form.
The described unit illustrated as separating component can be or may not be physically separate, shows as unit
The parts shown can be or may not be physical location, i.e. may be located at a place, or can also be distributed to multiple
On NE.Some or all of unit therein can be selected according to the actual needs to realize the mesh of the present embodiment scheme
's.
It addition, each functional unit in each embodiment of the present invention can be integrated in a processing unit, it is also possible to
It is that unit is individually physically present, it is also possible to two or more unit are integrated in a unit.Above-mentioned integrated list
Unit both can realize to use the form of hardware, it would however also be possible to employ hardware adds the form of SFU software functional unit and realizes.
The above-mentioned integrated unit realized with the form of SFU software functional unit, can be stored in an embodied on computer readable and deposit
In storage media.Above-mentioned SFU software functional unit is stored in a storage medium, including some instructions with so that a computer
Equipment (can be personal computer, server, or the network equipment etc.) or processor (processor) perform the present invention each
The part steps of method described in embodiment.And aforesaid storage medium includes: USB flash disk, portable hard drive, read only memory (Read-
Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disc or CD etc. various
The medium of program code can be stored.
Those skilled in the art are it can be understood that arrive, for convenience and simplicity of description, only with above-mentioned each functional module
Division be illustrated, in actual application, can be as desired by complete by different functional modules for above-mentioned functions distribution
Become, the internal structure of device will be divided into different functional modules, to complete all or part of function described above.On
State the specific works process of the device of description, be referred to the corresponding process in preceding method embodiment, do not repeat them here.
Last it is noted that various embodiments above is only in order to illustrate technical scheme, it is not intended to limit；To the greatest extent
The present invention has been described in detail by pipe with reference to foregoing embodiments, it will be understood by those within the art that: it depends on
So the technical scheme described in foregoing embodiments can be modified, or the most some or all of technical characteristic is entered
Row equivalent；And these amendments or replacement, do not make the essence of appropriate technical solution depart from various embodiments of the present invention technology
The scope of scheme.
Claims (13)
1. the communication means between a container, it is characterised in that including:
First virtual bridge sends Address requests message to coordinating network element, and described Address requests message includes the private network of target container
Address, so that described coordination network element obtains the public network address of described target container according to the private net address of described target container；
Described first virtual bridge receives the public network address of the described target container that described coordination network element sends；
Described first virtual bridge according to the public network address of described target container to the message of the second virtual bridge transmission source container,
So that described message is sent to described target container by described second virtual bridge；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual bridge and
Described target container is positioned at the 2nd Docker server.
Method the most according to claim 1, it is characterised in that described Address requests message also includes the private of described source container
Net address.
Method the most according to claim 2, it is characterised in that described first virtual bridge is asked to coordinating network element transmission address
Before seeking message, also include:
First virtual bridge distributes private net address to described source container；
Described first virtual bridge sends private net address and the public network of described source container of described source container to described coordination network element
Address, the public network address of described source container includes that public network IP address and port numbers, described public network IP address are described first
The IP address of Docker server.
4. the communication means between a container, it is characterised in that including:
Coordinating network element and receive the Address requests message that the first virtual bridge sends, described Address requests message includes target container
Private net address；
Described coordination network element obtains the public network address of described target container according to the private net address of described target container；
Described coordination network element sends the public network address of described target container to described first virtual bridge, so that described first virtual
Bridge according to the public network address of described target container to the message of the second virtual bridge transmission source container so that described second virtual
Described message is sent to described target container by bridge；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual bridge and
Described target container is positioned at the 2nd Docker server.
Method the most according to claim 4, it is characterised in that described coordination network element is according to the private network ground of described target container
Location obtains the public network address of described target container, including:
Described coordination network element inquires about Database Lists according to the private net address of described target container, and described Database Lists includes pre-
If the private net address of container and the public network address of described default container；
If described Database Lists includes the private net address of the default container mated with the private net address of described target container, then institute
State and coordinate network element and determine that the public network address of described target container is the public network address of described default container.
Method the most according to claim 5, it is characterised in that described coordination network element receives the ground that the first virtual bridge sends
Before the request message of location, also include:
Described coordination network element receives the private net address of described source container that described first virtual bridge sends and described source container
Public network address, the private net address of described source container is described first virtual bridge private net address to the distribution of described source container；Institute
The public network address stating source container includes that public network IP address and port numbers, described public network IP address are described Docker servers
IP address；
The private net address of described source container and the public network address of described source container are stored in Database Lists by described coordination network element.
7. a virtual bridge, it is characterised in that including:
Sending module, for coordinating network element transmission Address requests message, described Address requests message includes the private of target container
Net address, so that described coordination network element obtains the public network address of described target container according to the private net address of described target container；
Receiver module, for receiving the public network address of the described target container that described coordination network element sends；
Described sending module is additionally operable to the report to other virtual bridge transmission source containers of the public network address according to described target container
Literary composition, so that described message is sent to described target container by other virtual bridges described；
Wherein, described virtual bridge and described source container are positioned at a Docker server, other virtual bridges described and described
Target container is positioned at the 2nd Docker server.
Virtual bridge the most according to claim 7, it is characterised in that described Address requests message also includes described source container
Private net address.
Virtual bridge the most according to claim 8, it is characterised in that also include:
Distribution module, for distributing private net address to described source container；
Described sending module is additionally operable to send private net address and the public affairs of described source container of described source container to described coordination network element
Net address, the public network address of described source container includes that public network IP address and port numbers, described public network IP address are described first
The IP address of Docker server.
10. coordinate network element for one kind, it is characterised in that including:
Receiver module, for receiving the Address requests message that the first virtual bridge sends, described Address requests message includes target
The private net address of container；
Acquisition module, for obtaining the public network address of described target container according to the private net address of described target container；
Sending module, for sending the public network address of described target container, so that described first is empty to described first virtual bridge
Intend bridge according to the public network address of described target container to the message of the second virtual bridge transmission source container, so that described second is empty
Intend bridge and described message is sent to described target container；
Wherein, described first virtual bridge and described source container are positioned at a Docker server, described second virtual bridge and
Described target container is positioned at the 2nd Docker server.
11. coordination network elements according to claim 10, it is characterised in that described acquisition module includes:
Query unit, inquires about Database Lists for the private net address according to described target container, and described Database Lists includes
Preset private net address and the public network address of described default container of container；
Determine unit, if the default container including mating with the private net address of described target container for described Database Lists
Private net address, it is determined that the public network address of described target container is the public network address of described default container.
12. coordination network elements according to claim 11, it is characterised in that described receiver module is additionally operable to receive described first
The private net address of the described source container that virtual bridge sends and the public network address of described source container, the private net address of described source container
It it is described first virtual bridge private net address to the distribution of described source container；The public network address of described source container includes public network IP ground
Location and port numbers, described public network IP address is the IP address of a described Docker server；
Described coordination network element also includes memory module, is used for the public network ground of the private net address by described source container and described source container
Location is stored in Database Lists.
Communication system between 13. 1 kinds of containers, it is characterised in that include the virtual bridge as described in any one of claim 7-9
And the coordination network element as described in any one of claim 10-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610350477.1A CN106067858B (en) | 2016-05-24 | 2016-05-24 | Communication means, apparatus and system between container |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610350477.1A CN106067858B (en) | 2016-05-24 | 2016-05-24 | Communication means, apparatus and system between container |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106067858A true CN106067858A (en) | 2016-11-02 |
| CN106067858B CN106067858B (en) | 2019-02-15 |
Family
ID=57420701
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610350477.1A Active CN106067858B (en) | 2016-05-24 | 2016-05-24 | Communication means, apparatus and system between container |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106067858B (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106453614A (en) * | 2016-11-11 | 2017-02-22 | 郑州云海信息技术有限公司 | Cloud operation system and access method thereof |
| CN107395781A (en) * | 2017-06-29 | 2017-11-24 | 北京小度信息科技有限公司 | Network communication method and device |
| CN107395762A (en) * | 2017-08-30 | 2017-11-24 | 四川长虹电器股份有限公司 | A kind of application service based on Docker containers accesses system and method |
| CN107566541A (en) * | 2017-08-03 | 2018-01-09 | 携程旅游信息技术（上海）有限公司 | Capacitor network resource allocation methods, system, storage medium and electronic equipment |
| CN108574705A (en) * | 2017-03-09 | 2018-09-25 | 中国移动通信集团湖北有限公司 | Communication means, apparatus and system between a kind of container |
| CN108833163A (en) * | 2018-06-13 | 2018-11-16 | 平安科技（深圳）有限公司 | Creation method, device, computer equipment and the storage medium of Linux virtual server |
| CN111262784A (en) * | 2020-01-13 | 2020-06-09 | 杭州朗和科技有限公司 | Message forwarding method, message forwarding device, storage medium and electronic equipment |
| CN111510515A (en) * | 2020-04-07 | 2020-08-07 | 中国建设银行股份有限公司 | Method and device for distinguishing containers of mixed application environment |
| CN111654559A (en) * | 2020-05-29 | 2020-09-11 | 深圳前海微众银行股份有限公司 | Container data transmission method and device |
| CN112532675A (en) * | 2019-09-19 | 2021-03-19 | 贵州白山云科技股份有限公司 | Method, device and medium for establishing network edge computing system |
| CN112565275A (en) * | 2020-12-10 | 2021-03-26 | 杭州安恒信息技术股份有限公司 | Anomaly detection method, device, equipment and medium for network security scene |
| CN114301913A (en) * | 2021-12-24 | 2022-04-08 | 杭州萤石软件有限公司 | Request processing method and system |
| CN114422295A (en) * | 2021-12-27 | 2022-04-29 | 联想(北京)有限公司 | Network information processing method, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104951360A (en) * | 2015-06-30 | 2015-09-30 | 北京奇虎科技有限公司 | Configuration management mode and device based on Docker |
| CN104991815A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Docker container management method and system |
| CN105072115A (en) * | 2015-08-12 | 2015-11-18 | 国家电网公司 | Information system invasion detection method based on Docker virtualization |
| CN105490910A (en) * | 2014-09-19 | 2016-04-13 | 北京奇虎科技有限公司 | Network communication method and client |
| CN105511943A (en) * | 2015-12-03 | 2016-04-20 | 华为技术有限公司 | Docker container running method and device |
-
2016
- 2016-05-24 CN CN201610350477.1A patent/CN106067858B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105490910A (en) * | 2014-09-19 | 2016-04-13 | 北京奇虎科技有限公司 | Network communication method and client |
| CN104991815A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Docker container management method and system |
| CN104951360A (en) * | 2015-06-30 | 2015-09-30 | 北京奇虎科技有限公司 | Configuration management mode and device based on Docker |
| CN105072115A (en) * | 2015-08-12 | 2015-11-18 | 国家电网公司 | Information system invasion detection method based on Docker virtualization |
| CN105511943A (en) * | 2015-12-03 | 2016-04-20 | 华为技术有限公司 | Docker container running method and device |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106453614B (en) * | 2016-11-11 | 2019-06-18 | 郑州云海信息技术有限公司 | A kind of cloud operating system and its access method |
| CN106453614A (en) * | 2016-11-11 | 2017-02-22 | 郑州云海信息技术有限公司 | Cloud operation system and access method thereof |
| CN108574705A (en) * | 2017-03-09 | 2018-09-25 | 中国移动通信集团湖北有限公司 | Communication means, apparatus and system between a kind of container |
| CN107395781A (en) * | 2017-06-29 | 2017-11-24 | 北京小度信息科技有限公司 | Network communication method and device |
| CN107566541A (en) * | 2017-08-03 | 2018-01-09 | 携程旅游信息技术（上海）有限公司 | Capacitor network resource allocation methods, system, storage medium and electronic equipment |
| CN107395762A (en) * | 2017-08-30 | 2017-11-24 | 四川长虹电器股份有限公司 | A kind of application service based on Docker containers accesses system and method |
| CN108833163A (en) * | 2018-06-13 | 2018-11-16 | 平安科技（深圳）有限公司 | Creation method, device, computer equipment and the storage medium of Linux virtual server |
| CN108833163B (en) * | 2018-06-13 | 2020-08-28 | 平安科技（深圳）有限公司 | Linux virtual server creating method and device, computer equipment and storage medium |
| CN112532675A (en) * | 2019-09-19 | 2021-03-19 | 贵州白山云科技股份有限公司 | Method, device and medium for establishing network edge computing system |
| CN112532675B (en) * | 2019-09-19 | 2023-04-18 | 贵州白山云科技股份有限公司 | Method, device and medium for establishing network edge computing system |
| CN111262784B (en) * | 2020-01-13 | 2022-05-17 | 杭州朗和科技有限公司 | Message forwarding method, message forwarding device, storage medium and electronic equipment |
| CN111262784A (en) * | 2020-01-13 | 2020-06-09 | 杭州朗和科技有限公司 | Message forwarding method, message forwarding device, storage medium and electronic equipment |
| CN111510515A (en) * | 2020-04-07 | 2020-08-07 | 中国建设银行股份有限公司 | Method and device for distinguishing containers of mixed application environment |
| CN111654559A (en) * | 2020-05-29 | 2020-09-11 | 深圳前海微众银行股份有限公司 | Container data transmission method and device |
| CN111654559B (en) * | 2020-05-29 | 2023-04-07 | 深圳前海微众银行股份有限公司 | Container data transmission method and device |
| CN112565275A (en) * | 2020-12-10 | 2021-03-26 | 杭州安恒信息技术股份有限公司 | Anomaly detection method, device, equipment and medium for network security scene |
| CN112565275B (en) * | 2020-12-10 | 2022-09-20 | 杭州安恒信息技术股份有限公司 | Anomaly detection method, device, equipment and medium for network security scene |
| CN114301913A (en) * | 2021-12-24 | 2022-04-08 | 杭州萤石软件有限公司 | Request processing method and system |
| CN114301913B (en) * | 2021-12-24 | 2024-03-08 | 杭州萤石软件有限公司 | Request processing method and system |
| CN114422295A (en) * | 2021-12-27 | 2022-04-29 | 联想(北京)有限公司 | Network information processing method, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106067858B (en) | 2019-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106067858A (en) | Communication means between container, Apparatus and system | |
| CN105075226B (en) | So that mobile subscriber identification information can be by the method, system and medium of application access | |
| CN109871224A (en) | A kind of gray scale dissemination method, system, medium and equipment based on user identifier | |
| CN109672714B (en) | Data processing method of distributed storage system and distributed storage system | |
| CN109669955B (en) | Digital asset query system and method based on block chain | |
| CN106169994A (en) | The method of controlling security communicated between container and device | |
| CN105847108A (en) | Method and apparatus for communication between containers | |
| CN105701112A (en) | Data processing method, apparatus and system | |
| CN103596066A (en) | Method and device for data processing | |
| CN106899669B (en) | Registration-based enterprise container mirror image establishing method and device | |
| CN110351362A (en) | Data verification method, equipment and computer readable storage medium | |
| CN102739821A (en) | Method and system for allocating IP addresses | |
| CN110351364A (en) | Date storage method, equipment and computer readable storage medium | |
| CN108259605A (en) | A kind of data calling system and method based on multiple data centers | |
| CN106210162A (en) | Communication control method and device | |
| CN105978744B (en) | A kind of resource allocation methods, apparatus and system | |
| CN106028311A (en) | Terminal register method and device | |
| CN105872130A (en) | Method for distributing IP (Internet Protocol) addresses and cloud management platform | |
| CN103905375B (en) | Data encryption request distribution method and device in concentrating type data encryption system | |
| WO2017167129A1 (en) | Method and device for distributing data center data to user | |
| CN112003957B (en) | Method, device, server and storage medium for scheduling access point | |
| CN101741861B (en) | Data storage method and device | |
| CN111683164B (en) | IP address configuration method and VPN service system | |
| CN101345684A (en) | P2P node administration method | |
| CN106131237A (en) | Communication control method and device between container |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |