CN105824688A - Method for solving start concurrence bottleneck of docker container - Google Patents
Method for solving start concurrence bottleneck of docker container Download PDFInfo
- Publication number
- CN105824688A CN105824688A CN201610149449.3A CN201610149449A CN105824688A CN 105824688 A CN105824688 A CN 105824688A CN 201610149449 A CN201610149449 A CN 201610149449A CN 105824688 A CN105824688 A CN 105824688A
- Authority
- CN
- China
- Prior art keywords
- container
- docker
- docker container
- management platform
- fixed direction
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45508—Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method for solving a start concurrence bottleneck of a docker container. Through modifying the source code of a docker, the problem of the start concurrence of the docker container is solved; in a start process, the communication with a management platform is carried out; the network parameter of the docker container is directionally distributed according to the inquiry result of the management platform, so that the locking and the unlocking are avoided in a distribution process; further, the start concurrency of the docker container is improved; the blockage of a container queue cannot occur in the process of starting many containers.
Description
Technical field
The present invention relates to computer realm, be specifically related to a kind of method solving the docker container concurrent bottleneck of startup.
Background technology
Docker is a senior container engine based on LXC of PaaS provider dotCloud exploitation, source code trustship is on Github, docker is based on go language and defers to Apache2.0 agreement and increases income, developer can be packed their application and rely on bag in a transplantable container, then it is published on any popular Linux machine, it is also possible to realize virtualization.
Docker container is to use sandbox mechanism completely, does not the most have any interface (app of similar iPhone).Almost without performance cost, can run in machine and data center easily.The most important thing is, they do not rely on any language, framework includes system.
Build standardized running environment based on docker and be different from existing technical scheme, and it can be avoided that the defect of prior art existence.Currently existing scheme is to run a set of puppet/chef, or an image file on a baseOS mostly, but both technical schemes are the most perfect, and the former needs baseOS to provide many preconditions and the latter can revise hardly；Additionally, the latter's file size is big, environmental management and Version Control itself are also problems.
Due to the docker virtualized feature of lightweight based on LXC, docker compares the most obvious feature of KVM etc and starts exactly soon, and resource occupation is little.This is primarily due to LXC and has the feature of lightweight, start fast, and docker can only load the part of each container change, such resource occupation is little, it is possible to can more quickly and take less resource compared with the virtualization scheme of KVM etc under stand-alone environment
The network schemer of docker includes host, container, none and bridge:
(1) host pattern: an independent NetworkNamespace will not be obtained the when of starting container, but share a NetworkNamespace with host, container will not fictionalize the network interface card of oneself, configures the IP etc. of oneself, but uses IP and the port of host；
(2) container pattern: this pattern specifies newly created container and the container existed share a NetworkNamespace rather than share with host；Newly created container will not create the network interface card of oneself, configure the IP of oneself, but share IP, port range etc. with a container specified, equally, two containers are except network facet, other as file system, process list etc. or isolation, the process of two containers can be communicated by lO network card equipment；
(3) none pattern: this pattern is different with the first two；In such a mode, Docker container has the NetworkNamespace of oneself, but, do not carry out any network configuration for Docker container, it is to say, this Docker container does not has the information such as network interface card, IP, route, us are needed oneself to add network interface card, configuration of IP etc. for Docker container；
(4) bridge pattern: bridge pattern is the network settings of Docker acquiescence, this pattern can be each container allocation NetworkNamespace, arrange IP etc., and is connected on a virtual bridge by the Docker container on a main frame.
When docker container starts, if being provided with the network schemer of distribution IP, such as bridge, in this mode, verify for avoiding IP address conflict to need, as it is shown in figure 1, IP, mask can obtained, the gateway stage locks, without IP address conflict, then docker container is obtained in that network of relation parameter and starts, and otherwise returns mistake；During locking, other container needs to wait in line, and causes the obstruction of container queue.
Summary of the invention
In order to solve above-mentioned technical problem, the invention provides a kind of method solving the docker container concurrent bottleneck of startup.The present invention, by revising the source code of docker, relies on and peripheral device communication, it is achieved the fixed direction allocation to docker network parameter, thus improves the concurrency performance that container starts so that container queue will not be blocked during a large amount of containers start.
The present invention realizes with following technical scheme, a kind of method solving the docker container concurrent bottleneck of startup, comprises the following steps:
S1. inquiry docker container Starting mode, if the network schemer of distribution IP, then carries out S2；If the network schemer of non-distribution IP, the most normally start；
S2. docker container identification is obtained；
S3. by the transmission of docker container identification to described docker Container Management platform；
The most described docker Container Management platform inquires about docker fixed direction allocation log according to described docker container identification, if Query Result is empty, then returns mistake, and described docker container can not start；If Query Result is not empty, then network parameter transmission corresponding with described docker container identification in docker fixed direction allocation log is started to described docker container, described docker container according to the network parameter obtained.
Preferably, described docker fixed direction allocation log is for recording the corresponding relation of the docker container network parameter corresponding with described docker container.
Preferably, described docker Container Management platform, for managing the record in described docker fixed direction allocation log, is modified including to the record in described docker fixed direction allocation log, increase and/or is deleted.
Preferably, described container identification is specially Container Name.
Preferably, described container identification is specially Container ID.
Preferably, described network parameter includes: the IP of container, the mask of container, the gateway of container.
Preferably, described docker Container Management platform is additionally operable to the corresponding relation managing described container with described container self attributes.
Preferably, described container self attributes includes: container grouping information and container running status.
Described docker Container Management platform manages the corresponding relation of described container and described container self attributes by Container Management log.
Described Container Management log includes the contents such as ID, Container ID, Container Name, hostname, command, slave node, group packet, running status, establishment time and associative operation, and described associative operation includes starting, stopping and restarting.
Described docker Container Management platform can also carry out ASSOCIATE STATISTICS to the content in described Container Management log, described statistical content includes but not limited to container sum statistics, container running status statistics, classified statistics, slave node statistics, IP resource pool statistics and available resources statistics, and described container running status includes running and stopping.
Preferably, said method is applied to docker container start and also need to following steps:
(1) source code of docker application container engine is downloaded；
(2) according to described method, described source code is modified；
(3) compile described source code, and generate the executable program for starting docker；
(4) docker Container Management platform is created；
(5) run described executable program and docker Container Management platform simultaneously.
The invention has the beneficial effects as follows:
The invention provides a kind of method solving the docker container concurrent bottleneck of startup.The present invention, by revising the source code of docker, relies on and peripheral device communication, it is achieved the fixed direction allocation to docker network parameter, thus improves the concurrency performance that container starts so that container queue will not be blocked during a large amount of containers start.
Accompanying drawing explanation
Fig. 1 is that in prior art, docker container carries out the flow chart verified when starting；
Flow chart when Fig. 2 is that in embodiment, docker container starts；
Fig. 3 is the Organization Chart of docker container start-up course.
Detailed description of the invention
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with accompanying drawing, the present invention is described in further detail.
In one embodiment, solve, as in figure 2 it is shown, a kind of, the method that docker container starts concurrent bottleneck, comprise the following steps:
S1. inquiry docker container Starting mode, if the network schemer of distribution IP, then carries out S2；If the network schemer of non-distribution IP, the most normally start；
S2. obtain docker Container Name, and connect docker Container Management platform；
S3. by the transmission of docker Container Name to described docker Container Management platform；
The most described docker Container Management platform inquires about docker fixed direction allocation log according to described docker Container Name, if Query Result is not empty, then carries out S5；If Query Result is empty, then returning mistake, described docker container can not start；
S5. by network parameter transmission corresponding with described docker Container Name in docker fixed direction allocation log to described docker container, described docker fixed direction allocation log is for recording the corresponding relation of the docker container network parameter corresponding with described docker container；
S6.docker container starts according to the network parameter obtained.
Described method is applied to docker container start and also need to following steps:
(1) source code of docker application container engine is downloaded；
(2) according to described method, described source code is modified；
(3) compile described source code, and generate the executable program for starting docker；
(4) docker Container Management platform is created；
(5) run described executable program and docker Container Management platform simultaneously.
Described docker Container Management platform, for managing the record in described docker fixed direction allocation log, is modified including to the record in described docker fixed direction allocation log, increase and/or is deleted；Described network parameter includes: the IP of container, the mask of container, the gateway of container.
If described docker container does not exists in fixed direction allocation log, then start and mistake occurs, and point out docker container described in manager not exist, described manager is by adding described docker container in described docker fixed direction allocation table, and after being described docker container configuration network parameter, update described docker fixed direction allocation log.After described docker orientation log is updated, described docker container can normally start.
Described docker fixed direction allocation log is as shown in table 1:
Table 1docker fixed direction allocation log
Described docker Container Management platform is additionally operable to the corresponding relation managing described container with described container self attributes；Described container self attributes includes: container grouping information and container running status.
Described docker Container Management platform manages the corresponding relation of described container and described container self attributes by Container Management log.
Described Container Management log includes the contents such as ID, Container ID, Container Name, hostname, command, slave node, group packet, running status, establishment time and associative operation, and described associative operation includes starting, stopping and restarting.
Described docker Container Management platform relies on mysql to research and develop.Mysql is a Relational DBMS, MySQLAB company of Sweden develop, belong to company under Oracle at present.The most popular Relational DBMS of mysql, in terms of WEB application, mysql is one of best RDBMS (RelationalDatabaseManagementSystem, relational database management system) application software.Mysql is a kind of associated data library management system, and linked database saves the data in different tables rather than all data is placed in a big warehouse, which adds speed and improve motility.The sql like language that mysql is used is the most frequently used standardized language for accessing data base.Mysql volume is little, speed is fast, the total cost of ownership is low, especially this feature of open source code so that mysql becomes the preference data storehouse building docker Container Management platform, and docker also is able to carry out communication with mysql data base.
Second embodiment, in the present embodiment, the Organization Chart of docker container start-up course is as shown in Figure 3, docker container start-up course needs to rely on 5 modules in needing, and is DockerDaemon, DockerClient respectively, Driver, Libcontainer and Container, wherein Driver also includes networkdriver, graphdriver and execdriver.
DockerDaemon is the finger daemon operating in backstage in Docker framework, substantially can be divided into DockerServer, Engine and Job tri-part.DockerDaemon may be considered the request being accepted DockerClient by DockerServer module, and processes request in Engine, then according to request type, is created that the Job specified and runs.
DockerDaemon Yu Driver interacts, carrying out practically process has following several possible: obtain mirror image to DockerRegistry, the localization being performed container mirror image by graphdriver is operated, performed the configuration of capacitor network environment by networkdriver, performed the execution work etc. of container internal operation by execdriver
Libcontainer is the bag in Docker for Container Management, and it realizes based on Go language, carries out container control by management namespaces, cgroups, capabilities and file system.Libcontainer creates container, and container is carried out life cycle management.As long as achieving a group interface of Libcontainer definition, Docker can run, and this just brings possibility for Docker realization is the most cross-platform.In general, Libcontainer itself is broadly divided into three bulk job contents, and one is establishment and the initialization of container, and two is container life cycle management, and three is management of process
Container object mainly contain container configuration, control, state such as shows at the function, is abstract to different platform container function.It is thread-safe inside each Container process.Because Container is likely destroyed by outside process, so whether container can be existed by each method detect.
This module architectures is the necessary framework starting docker, in the prior art, due to docker container allocation IP and mask, it is thus desirable to this process is locked, if the when of container batch operation in the cluster, it is easy for causing obstruction, and in this, obstruction has resulted in overstocking of the startup queue of container, thus have influence on efficiency and the stability that container starts；By revising the source code of docker in the present embodiment, rely on and peripheral device communication, and described docker fixed direction allocation log is achieved on external equipment, it is achieved thereby that the fixed direction allocation to docker network parameter, avoid the process locking and unlocking, this allow in the cluster batch operation when, it is possible to be rapidly performed by the startup of container, overcome the concurrent bottleneck problem in container start-up course.
It is being that a kind of of research and development under the framework of this example solves the method that docker container starts concurrent bottleneck, is comprising the following steps:
S1. inquiry docker container Starting mode, if the network schemer of distribution IP, then carries out S2；If the network schemer of non-distribution IP, the most normally start；
S2. obtain docker Container Name, and connect docker Container Management platform；
S3. by the transmission of docker Container Name to described docker Container Management platform；
The most described docker Container Management platform inquires about docker fixed direction allocation log according to described docker Container Name, if Query Result is not empty, then carries out S5；If Query Result is empty, then returning mistake, described docker container can not start；
S5. by network parameter transmission corresponding with described docker Container Name in docker fixed direction allocation log to described docker container, described docker fixed direction allocation log is for recording the corresponding relation of the docker container network parameter corresponding with described docker container；
S6.docker container starts according to the network parameter obtained.
Described method is applied to docker container start and also need to following steps:
(1) source code of docker application container engine is downloaded；
(2) according to described method, described source code is modified；
(3) compile described source code, and generate the executable program for starting docker；
(4) docker Container Management platform is created；
(5) run described executable program and docker Container Management platform simultaneously.
Described docker Container Management platform, for managing the record in described docker fixed direction allocation log, is modified including to the record in described docker fixed direction allocation log, increase and/or is deleted；Described network parameter includes: the IP of container, the mask of container, the gateway of container.
If described docker container does not exists in fixed direction allocation log, then start and mistake occurs, and point out docker container described in manager not exist, described manager is by adding described docker container in described docker fixed direction allocation table, and after being described docker container configuration network parameter, update described docker fixed direction allocation log.After described docker orientation log is re-updated, described docker container can normally start.
Described docker Container Management platform is additionally operable to the corresponding relation managing described container with described container self attributes；Described container self attributes includes: container grouping information and container running status.
Described docker Container Management platform manages the corresponding relation of described container and described container self attributes by Container Management log.
Described Container Management log includes the contents such as ID, Container ID, Container Name, hostname, command, slave node, group packet, running status, establishment time and associative operation, and described associative operation includes starting, stopping and restarting.
In addition, the present embodiment also including, described docker Container Management platform carries out ASSOCIATE STATISTICS to the content in described Container Management log, described statistical content includes container sum statistics, container running status statistics, classified statistics, slave node statistics, IP resource pool statistics and available resources statistics, and in the present embodiment, docker Container Management platform statistical table is as shown in table 2.
Table 2docker Container Management platform statistical table
Described docker Container Management platform includes docker fixed direction allocation log, Container Management log and docker Container Management platform statistical table, and described docker Container Management platform relies on mysql to research and develop, and above-mentioned three tables are carried out integrated management.
3rd embodiment, docker container start-up course needs to rely on 5 modules in needing, is DockerDaemon respectively, DockerClient, Driver, Libcontainer and Container, wherein Driver also includes networkdriver, graphdriver and execdriver.
Rely on above-mentioned 5 modules to solve the method that docker container starts concurrent bottleneck, comprise the following steps:
S1. inquiry docker container Starting mode, if the network schemer of distribution IP, then carries out S2；If the network schemer of non-distribution IP, the most normally start；
S2. obtain docker Container ID, and connect docker Container Management platform；
S3. by the transmission of docker Container ID to described docker Container Management platform；
The most described docker Container Management platform inquires about docker fixed direction allocation log according to described docker Container ID, if Query Result is not empty, then carries out S5；If Query Result is empty, then returning mistake, described docker container can not start；
S5. by network parameter transmission corresponding with described docker Container ID in docker fixed direction allocation log to described docker container, described docker fixed direction allocation log is for recording the corresponding relation of the docker container network parameter corresponding with described docker container；
S6.docker container starts according to the network parameter obtained；Described network parameter includes: the IP of container, the mask of container, the gateway of container.
Described method is applied to docker container start and also need to following steps:
(1) source code of docker application container engine is downloaded；
(2) according to described method, described source code is modified；
(3) compile described source code, and generate the executable program for starting docker；
(4) docker Container Management platform is created；
(5) run described executable program and docker Container Management platform simultaneously.
Described docker Container Management platform, for managing the record in described docker fixed direction allocation log, is modified including to the record in described docker fixed direction allocation log, increase and/or is deleted；Described network parameter includes: the IP of container, the mask of container, the gateway of container.
If described docker container does not exists in fixed direction allocation log, then start and mistake occurs, and point out docker container described in manager not exist, described manager is by adding described docker container in described docker fixed direction allocation table, and after being described docker container configuration network parameter, update described docker fixed direction allocation log.After described docker orientation log is re-updated, described docker container can normally start.
Described docker fixed direction allocation log is as shown in table 3:
Table 3docker fixed direction allocation log
Described docker Container Management platform is additionally operable to the corresponding relation managing described container with described container self attributes；Described container self attributes includes: container grouping information and container running status.
Described docker Container Management platform manages the corresponding relation of described container and described container self attributes by Container Management log.
Described Container Management log includes the contents such as ID, Container ID, Container Name, hostname, command, slave node, group packet, running status, establishment time and associative operation, and described associative operation includes starting, stopping and restarting.
Described docker Container Management platform uses docker Container Management platform statistical table that the content in described Container Management log carries out ASSOCIATE STATISTICS, and the content of described docker Container Management platform statistical table includes container sum statistics, container running status statistics, classified statistics, slave node statistics, IP resource pool statistics and available resources statistics.
The present embodiment also including, described docker Container Management platform is managed for IP resource pool, described docker Container Management platform uses IP resource pool management table to be managed described IP resource pool, described IP resource pool management table includes docker Container ID number corresponding to packet belonging to IP resource pool ID, IP resource pool title, IP resource pool, IP resource pool remarks, IP resource pool mask, IP resource pool mask annotation, IP resource pool gateway, IP resource pool gateway annotation, IP resource pool and the operation for described IP resource pool, and described operation includes revising and deletion.
Described docker Container Management platform includes docker fixed direction allocation log, Container Management log, IP resource pool management table and docker Container Management platform statistical table, described docker Container Management platform relies on mysql to research and develop, and above-mentioned four tables are carried out integrated management.
The above disclosed present pre-ferred embodiments that is only, certainly can not limit the interest field of the present invention, the equivalent variations therefore made according to the claims in the present invention with this, still belong to the scope that the present invention is contained.
Claims (8)
1. one kind solves the method that docker container starts concurrent bottleneck, it is characterised in that comprise the following steps:
S1. inquiry docker container Starting mode, if the network schemer of distribution IP, then carries out S2；If the network schemer of non-distribution IP, the most normally start；
S2. docker container identification is obtained；
S3. by the transmission of docker container identification to described docker Container Management platform；
The most described docker Container Management platform inquires about docker fixed direction allocation log according to described docker container identification, if Query Result is empty, then returns mistake, and described docker container can not start；If Query Result is not empty, then network parameter transmission corresponding with described docker container identification in docker fixed direction allocation log is started to described docker container, described docker container according to the network parameter obtained.
A kind of method solving the docker container concurrent bottleneck of startup the most according to claim 1, it is characterised in that described docker fixed direction allocation log is for recording the corresponding relation of the docker container network parameter corresponding with described docker container.
A kind of method solving the docker container concurrent bottleneck of startup the most according to claim 1, it is characterized in that, described docker Container Management platform, for managing the record in described docker fixed direction allocation log, is modified including to the record in described docker fixed direction allocation log, increase and/or is deleted.
4. according to a kind of method solving the docker container concurrent bottleneck of startup described in any one in claim 1-3, it is characterised in that described container identification is specially Container Name.
5. according to a kind of method solving the docker container concurrent bottleneck of startup described in any one in claim 1-3, it is characterised in that described container identification is specially Container ID.
A kind of method solving the docker container concurrent bottleneck of startup the most according to claim 1, it is characterised in that described network parameter includes: the IP of container, the mask of container, the gateway of container.
A kind of method solving the docker container concurrent bottleneck of startup the most according to claim 1, it is characterised in that described docker Container Management platform is additionally operable to the corresponding relation managing described container with described container self attributes.
A kind of method solving the docker container concurrent bottleneck of startup the most according to claim 7, it is characterised in that described container self attributes includes: container grouping information and container running status.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610149449.3A CN105824688B (en) | 2016-03-16 | 2016-03-16 | A method of it solving docker container and starts concurrent bottleneck |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610149449.3A CN105824688B (en) | 2016-03-16 | 2016-03-16 | A method of it solving docker container and starts concurrent bottleneck |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105824688A true CN105824688A (en) | 2016-08-03 |
| CN105824688B CN105824688B (en) | 2019-05-28 |
Family
ID=56987796
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610149449.3A Active CN105824688B (en) | 2016-03-16 | 2016-03-16 | A method of it solving docker container and starts concurrent bottleneck |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105824688B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106686088A (en) * | 2016-12-30 | 2017-05-17 | 广东浪潮大数据研究有限公司 | Management method supporting multi-network mode of Docker environment |
| CN106878484A (en) * | 2017-02-27 | 2017-06-20 | 郑州云海信息技术有限公司 | A kind of method of configuration Docker cluster external containers IP |
| CN107665145A (en) * | 2016-07-29 | 2018-02-06 | 中国科学院声学研究所 | A kind of browser unit method for managing resource based on container |
| CN107704593A (en) * | 2017-10-12 | 2018-02-16 | 成都知道创宇信息技术有限公司 | It is a kind of to detect and solve the method that Docker locals mirror image conflicts with remote warehouse mirror image |
| CN108270838A (en) * | 2017-01-04 | 2018-07-10 | 中国科学院声学研究所 | A kind of browser HTML5 resource coordinating methods based on container |
| CN109213573A (en) * | 2018-09-14 | 2019-01-15 | 珠海国芯云科技有限公司 | The equipment blocking method and device of virtual desktop based on container |
| CN110995561A (en) * | 2019-12-06 | 2020-04-10 | 中国科学院信息工程研究所 | Virtual network data communication interaction method and system based on container technology |
| CN111355763A (en) * | 2018-12-24 | 2020-06-30 | 中移（杭州）信息技术有限公司 | Configuration file processing method, device, equipment and medium |
| CN111459573A (en) * | 2020-04-01 | 2020-07-28 | 济南浪潮高新科技投资发展有限公司 | Method and device for starting intelligent contract execution environment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104899126A (en) * | 2015-06-12 | 2015-09-09 | 北京奇虎科技有限公司 | Method, device and system for performing local real-time monitoring on containers in host |
| CN104991815A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Docker container management method and system |
| CN105069353A (en) * | 2015-08-11 | 2015-11-18 | 武汉大学 | Security reinforcement method for credible container based on Docker |
| CN105357296A (en) * | 2015-10-30 | 2016-02-24 | 河海大学 | Elastic caching system based on Docker cloud platform |
-
2016
- 2016-03-16 CN CN201610149449.3A patent/CN105824688B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104899126A (en) * | 2015-06-12 | 2015-09-09 | 北京奇虎科技有限公司 | Method, device and system for performing local real-time monitoring on containers in host |
| CN104991815A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Docker container management method and system |
| CN105069353A (en) * | 2015-08-11 | 2015-11-18 | 武汉大学 | Security reinforcement method for credible container based on Docker |
| CN105357296A (en) * | 2015-10-30 | 2016-02-24 | 河海大学 | Elastic caching system based on Docker cloud platform |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107665145B (en) * | 2016-07-29 | 2020-04-03 | 中国科学院声学研究所 | Browser stand-alone resource management method based on container |
| CN107665145A (en) * | 2016-07-29 | 2018-02-06 | 中国科学院声学研究所 | A kind of browser unit method for managing resource based on container |
| CN106686088A (en) * | 2016-12-30 | 2017-05-17 | 广东浪潮大数据研究有限公司 | Management method supporting multi-network mode of Docker environment |
| CN108270838A (en) * | 2017-01-04 | 2018-07-10 | 中国科学院声学研究所 | A kind of browser HTML5 resource coordinating methods based on container |
| CN108270838B (en) * | 2017-01-04 | 2020-04-24 | 中国科学院声学研究所 | Container-based browser HTML5 resource coordination method |
| CN106878484A (en) * | 2017-02-27 | 2017-06-20 | 郑州云海信息技术有限公司 | A kind of method of configuration Docker cluster external containers IP |
| CN107704593A (en) * | 2017-10-12 | 2018-02-16 | 成都知道创宇信息技术有限公司 | It is a kind of to detect and solve the method that Docker locals mirror image conflicts with remote warehouse mirror image |
| CN107704593B (en) * | 2017-10-12 | 2020-11-27 | 成都知道创宇信息技术有限公司 | Method for detecting and solving conflict between Docker local mirror image and remote warehouse mirror image |
| CN109213573A (en) * | 2018-09-14 | 2019-01-15 | 珠海国芯云科技有限公司 | The equipment blocking method and device of virtual desktop based on container |
| CN111355763A (en) * | 2018-12-24 | 2020-06-30 | 中移（杭州）信息技术有限公司 | Configuration file processing method, device, equipment and medium |
| CN111355763B (en) * | 2018-12-24 | 2022-11-15 | 中移（杭州）信息技术有限公司 | Configuration file processing method, device, equipment and medium |
| CN110995561A (en) * | 2019-12-06 | 2020-04-10 | 中国科学院信息工程研究所 | Virtual network data communication interaction method and system based on container technology |
| CN110995561B (en) * | 2019-12-06 | 2021-05-07 | 中国科学院信息工程研究所 | Virtual network data communication interaction method and system based on container technology |
| CN111459573A (en) * | 2020-04-01 | 2020-07-28 | 济南浪潮高新科技投资发展有限公司 | Method and device for starting intelligent contract execution environment |
| CN111459573B (en) * | 2020-04-01 | 2023-09-15 | 山东浪潮科学研究院有限公司 | Method and device for starting intelligent contract execution environment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105824688B (en) | 2019-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105824688A (en) | Method for solving start concurrence bottleneck of docker container | |
| US20220067025A1 (en) | Ordering transaction requests in a distributed database according to an independently assigned sequence | |
| US20180336365A1 (en) | Database public interface | |
| WO2023124967A1 (en) | Method for calling android hidl interface by software operating system, and device and medium | |
| CN111264048B (en) | Method for defining NSD for NS and instantiating NS and related network node | |
| US20170161511A1 (en) | Database public interface | |
| CN105740048A (en) | Image management method, device and system | |
| WO2012054192A2 (en) | Web service patterns for globally distributed service fabric | |
| CA2519010A1 (en) | Query framework system and method | |
| US20160253403A1 (en) | Object query model for analytics data access | |
| US20180314957A1 (en) | Inferring a label namespace | |
| CN108984236A (en) | A kind of implementation method and equipment of virtual management platform | |
| US8677354B2 (en) | Controlling kernel symbol visibility and accessibility across operating system linkage spaces | |
| US20230055129A1 (en) | Techniques for utilizing patterns and logical entities | |
| US11803373B1 (en) | Application versioning and upgrade | |
| US9843652B2 (en) | Context switch of database connections | |
| EP3462341B1 (en) | Local identifiers for database objects | |
| US11886551B2 (en) | Systems and methods for asset management | |
| US20110307908A1 (en) | Systems, methods, and computer program products providing an interface for one or more databases | |
| WO2022242635A1 (en) | Management device for sql records for maintenance and application system | |
| EP3405867B1 (en) | Database and service upgrade without downtime | |
| US20150134828A1 (en) | Infrastructure migration tool | |
| US20240126816A1 (en) | Self-discovery and construction of type-sensitive columnar formats on type-agnostic storage servers to accelerate offloaded queries | |
| US20240134830A1 (en) | Software services with declarative resource modeling and resource model patterns | |
| US11755311B1 (en) | Versioned schema |
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 | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 100080 Beijing Haidian District city Haidian street A Sinosteel International Plaza No. 8 block 5 layer A, C Patentee after: Youku network technology (Beijing) Co.,Ltd. Address before: 100080, A, 5, block 8, Sinosteel International Plaza, Haidian Avenue, Haidian District, Beijing Patentee before: 1VERGE INTERNET TECHNOLOGY (BEIJING) Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20200622 Address after: 310052 room 508, floor 5, building 4, No. 699, Wangshang Road, Changhe street, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Alibaba (China) Co.,Ltd. Address before: 100080 Beijing Haidian District city Haidian street A Sinosteel International Plaza No. 8 block 5 layer A, C Patentee before: Youku network technology (Beijing) Co.,Ltd. |