CN112835594A - Mirror image construction method and system based on Kubernetes - Google Patents
Mirror image construction method and system based on Kubernetes Download PDFInfo
- Publication number
- CN112835594A CN112835594A CN202110056693.6A CN202110056693A CN112835594A CN 112835594 A CN112835594 A CN 112835594A CN 202110056693 A CN202110056693 A CN 202110056693A CN 112835594 A CN112835594 A CN 112835594A
- Authority
- CN
- China
- Prior art keywords
- mirror image
- code
- construction
- dockerfile
- private
- 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.)
- Pending
Links
- 238000010276 construction Methods 0.000 title claims abstract description 109
- 238000000034 method Methods 0.000 claims abstract description 16
- 238000004519 manufacturing process Methods 0.000 claims abstract description 10
- 238000010367 cloning Methods 0.000 claims abstract description 7
- 238000002360 preparation method Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 7
- 239000000284 extract Substances 0.000 claims description 4
- 238000003860 storage Methods 0.000 claims description 4
- 238000004140 cleaning Methods 0.000 claims description 3
- 230000010354 integration Effects 0.000 abstract description 3
- 238000013459 approach Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Abstract
The invention provides a mirror image construction method based on Kubernetes and a construction system thereof, wherein the mirror image construction method based on Kubernetes comprises the following steps: preparing Dockerfile, mounting a public key and a private key of a private code library, cloning a source code to a specified directory, executing source code compiling to obtain a product, and copying the generated product to make a final mirror image; and (4) mirror image manufacturing, namely analyzing the prepared Dockerfile, executing mirror image construction, caching a mirror image layer, deleting a basic mirror image, and pushing the basic mirror image to a mirror image warehouse. By adopting the technical scheme of the invention, the mirror image volume can be effectively controlled, the safety of the private code base is ensured, the mirror image construction time is saved, the source code pulling and compiling as well as the integration of mirror image construction, pushing and caching can be realized, in the whole construction process, the CPU utilization rate is reduced by 90%, the memory utilization rate is reduced by 81%, and the construction time is shortened by 57%.
Description
Technical Field
The invention relates to the technical field of cloud protogenesis, in particular to a mirror image construction method and a mirror image construction system based on Kubernetes.
Background
Building a container image from a standard Dockerfile typically relies on interactive access to the node Docker daemon, which requires root access rights granted to the container to access the computer in order to operate. This has led to the difficulty of building container images in environments where their Docker daemon cannot be easily or securely exposed, such as the kubernets cluster. To mention the construction of container mirrors in kubernets, it was first thought to run DinD, i.e., Docker-in-Docker. DinD realizes the construction of container mirror images through an internal Docker, but the following problems exist in the method:
1. DinD requires a privileged mode to operate. When applications are deployed through kubernets, the privileged schema needs to be used. The mode allows the root in the container to have the root authority of the external host, can access all devices on the host, and can execute mount by mount. When the host computer disk device is mounted inside the container through mount, the container can acquire the read-write permission of the host computer file, and in addition, commands can be executed on the host computer through modes of writing in a plan task and the like, so that great potential safety hazards exist.
2. DinD depends on the Docker of the node. When an application is deployed once through kubernets, a dockerd process is added to the scheduled node. With the increase of application programs, when deployed applications are all scheduled to the same node, great pressure is brought to the node, and node resources are in shortage.
3. There is no cache available when DinD generates images. For the global secondary construction, the mirror layer produced last time and the required dependency cannot be reused, and a new layer needs to be regenerated, so that the construction time is increased, and the unfriendly construction experience is brought.
Building an image in a container has always been a security challenge because the file system of the node needs to be accessed to communicate with the Docker daemon. At present, the resource pressure of nodes in the existing technical scheme is large, the mirror image construction time is long, and the construction experience is not friendly.
Disclosure of Invention
Aiming at the technical problems, the invention discloses a mirror image construction method based on Kubernetes and a mirror image construction system thereof, which can construct a mirror image in a Kubernetes cluster more safely, reduce the resource pressure of nodes and shorten the mirror image construction time.
In contrast, the technical scheme adopted by the invention is as follows:
a mirror image construction method based on Kubernetes comprises the following steps:
preparing Dockerfile, mounting a public key and a private key of a private code library, cloning a source code to a specified directory, executing source code compiling to obtain a product, and copying the generated product to make a final mirror image;
and (4) mirror image manufacturing, namely analyzing the prepared Dockerfile, executing mirror image construction, caching a mirror image layer, deleting a basic mirror image, and pushing the basic mirror image to a mirror image warehouse.
As a further improvement of the invention, the preparation of the Dockerfile comprises a code compiling stage and a mirror image constructing stage, and in the process of preparing the Dockerfile, the content in the Dockerfile is named in stages;
in the code compiling stage, naming the content of the code compiling stage; in the mirror image construction stage, the product is obtained by naming the content in the code compiling stage, mirror image construction is completed, and renaming is carried out; and after the product is obtained, deleting the compiling environment and the product in the compiling stage.
With regard to the construction of container mirroring, how to control the mirrored volume is one of the core issues. In general, a Dockerfile constructed by an image includes not only a compiling environment of software but also an operating environment of a container, and in this case, the compiled image is very bulky and may leak source code. And the final image is operated without a compiling environment, and only the operating environment is needed. Another common method is to execute a script for compiling source codes to obtain a product, and additionally compile a Dockerfile only containing a program running environment, so that the final mirror volume is actually reduced, but the learning cost and the maintenance work are undoubtedly increased, and not only the script grammar and the Dockerfile grammar need to be learned, but also the compiled script and the Dockerfile need to be maintained. By adopting the technical scheme of the invention, the problem is solved by reasonably adjusting the content of the Dockerfile. In the prior art, a Dockerfile is generally adopted to construct and pack a code compiling environment into a final mirror image, and in the technical scheme, a staged name-taking design is carried out on the content in the Dockerfile, specifically, a first stage is used as a code compiling stage to compile a source code into a product; and in the second stage, the product is acquired through the name of the first stage to complete the construction of the mirror image. In the first stage, the code compiling environment and the product exist temporarily, and after the product is acquired in the second stage, the compiling environment and the product can be automatically cleaned. When the compilation environment and the artifact are cleaned, the mirror volume is naturally compressed.
As a further improvement of the invention, a certificate for pulling the code is obtained in a mode of temporarily mounting a public key and a private key in Dockerfile, and the private code library pulls the source code in Dockerfile.
Authentication authorization can be achieved using basic auth for the http/https protocol, but this requires access credentials for the SSH protocol. It is common practice to mount the public and private keys of the SSH protocol in a container, but this approach is very insecure, and the public and private keys exist in the finally generated mirror layer.
The invention is further improved, in the code compiling stage, SSH type mounting is used for temporarily mounting the public and private keys of the private code base, the private code base pulls the codes through an SSH protocol, and after the codes are pulled down and compiled successfully, the SSH public and private keys are automatically cleaned.
It is also a matter of consideration in the construction of the container image when the source code is pulled. In the existing method, a git client or an open-source tool for realizing git API is used in advance to pull a source code to a certain position such as a/workspace through an SSH/http/https protocol, and then the source code is switched to a source code directory to obtain a Dockerfile file to execute mirror image construction. However, this method results in a decentralization of the whole process and a poor construction experience. The invention is further improved, and the certificate of the pull code is obtained by temporarily mounting the public and private keys in the Dockerfile, so that the source code pull is realized in the Dockerfile.
As a further improvement of the invention, in the mirror image construction stage, an open source mirror image construction tool Kaniko is adopted to construct a mirror image. Kaniko, whose operation does not rely on the Docker daemon of the node, makes it easier and safer to build container images in those environments that do not have root access rights, such as the kubernets cluster.
As a further improvement of the present invention, the constructing the mirror image comprises the following steps: the method comprises the steps of assigning a Docker file path, a mirror image pushing address and a source code position to an executable program execotr of Kaniko, automatically extracting contents in the Docker file by the executable program execotr to serve as a file system of a container, then automatically completing construction of a mirror image, and pushing the mirror image to an assigned warehouse address and caching the mirror image for subsequent construction. By using Kaniko, the automatic construction is realized without manual intervention in the whole mirror image construction process.
The invention also discloses a mirror image construction system based on Kubernetes, which comprises the following steps:
the Dockerfile preparation module is used for preparing Dockerfile, mounting a public key and a private key of a private code library, cloning a source code to a specified directory, executing source code compiling to obtain a product, and copying the generated product to make a final mirror image;
and the mirror image manufacturing module is used for analyzing the prepared Dockerfile, executing mirror image construction, caching a mirror image layer, deleting a basic mirror image and pushing the basic mirror image to a mirror image warehouse.
As a further improvement of the invention, the Dockerfile preparation module comprises a naming module for naming the contents of the code compiling stage in the code compiling stage, and in the mirror image construction stage, acquiring the product by acquiring the naming of the contents of the code compiling stage, completing the construction of the mirror image, and then renaming;
the cleaning module is used for deleting the compiling environment and the product in the compiling stage after the product is obtained;
the code pulling module is used for temporarily mounting the public and private keys of the private code library by using SSH type mounting in a code compiling stage and obtaining a certificate of a pulling code, the private code library pulls the code in Dockerfile through an SSH protocol, and after the code is successfully pulled and compiled, the SSH public and private keys are automatically cleaned;
the mirror image manufacturing module comprises an open source mirror image construction tool Kaniko used for constructing mirror images.
As a further improvement of the present invention, the Dockerfile preparation module includes a mirror image construction module, which is used to assign a Dockerfile path, a mirror image push address and a source code position to an executable program executer of Kaniko, the executable program executer automatically extracts the content in the Dockerfile as a file system of a container, then automatically completes construction of the mirror image, and pushes the mirror image to an assigned warehouse address and caches the mirror image for subsequent construction.
The invention also discloses a computer readable storage medium, which is characterized by comprising a computer program, and when the computer program runs on a computer, the Kubernets-based image construction method is executed.
The invention also discloses a device which comprises a processor and a memory which are connected, and is characterized in that the processor is used for executing the computer program stored in the memory so as to execute the Kubernetes-based image construction method.
Compared with the prior art, the invention has the beneficial effects that:
by adopting the technical scheme of the invention, the mirror image volume can be effectively controlled, the safety of the private code base is ensured, the mirror image construction time is saved, and the source code pulling and compiling, mirror image construction, pushing and caching integration can be realized. In the whole construction process, the CPU utilization rate is reduced by 90%, the memory utilization rate is reduced by 81%, and the construction time (aiming at global secondary construction) is shortened by 57%. Compared with the DinD scheme, the Kaniko scheme of the invention saves computing resources, shortens construction time, improves host machine safety and improves user experience.
Drawings
FIG. 1 is a schematic flow chart of a mirror image construction method based on Kubernetes according to the present invention.
FIG. 2 is a comparison diagram of the utilization rate of a CPU based on the Kubernets mirror image construction method and the DinD scheme.
Fig. 3 is a comparison diagram of memory usage amounts of a kubernets-based mirror image construction method and a DinD scheme according to the present invention.
FIG. 4 is a comparison of the mirror image construction method based on Kubernets and the construction time using DinD scheme.
Detailed Description
Preferred embodiments of the present invention are described in further detail below.
As shown in fig. 1, a mirror image construction method based on Kubernetes includes:
1. preparing Dockerfile: mounting a public key and a private key of a private code library, cloning a source code to a specified directory, and executing source code compiling to obtain a product; copying the already created article to make the final image.
2. Mirror image manufacturing: and analyzing the prepared Dockerfile, and executing mirror image construction, caching and pushing to a mirror image warehouse.
With regard to the construction of container mirroring, there are three issues of comparison core:
(1) how to control the mirror volume. In general, a Dockerfile constructed by an image includes not only a compiling environment of software but also an operating environment of a container, and in this case, the compiled image is very bulky and may leak source code. And the final image is operated without a compiling environment, and only the operating environment is needed. Another common method is to execute a script for compiling source codes to obtain a product, and additionally compile a Dockerfile only containing a program running environment, so that the final mirror volume is actually reduced, but the learning cost and the maintenance work are undoubtedly increased, and not only the script grammar and the Dockerfile grammar need to be learned, but also the compiled script and the Dockerfile need to be maintained.
(2) The credential problem of pulling code through SSH protocol. Authentication authorization can be achieved using basic auth for the http/https protocol, but this requires access credentials for the SSH protocol. It is common practice to mount the public and private keys of the SSH protocol in a container, but this approach is very insecure, and the public and private keys exist in the finally generated mirror layer.
(3) When the source code is pulled. It is common practice to pull the source code to a location such as/workspace via SSH/http/https protocol using a git client or an open-source implementation of git API in advance. Switching to the source code directory again performs the mirror construction by getting the Dockerfile file, but this approach does not automate the CI/CD.
Aiming at the problem of controlling the mirror volume and the mirror volume, the Dockerfile content can be reasonably adjusted in the scheme. In the prior art, the Dockerfile constructs and packs the code compiling environment into a final mirror image together, which causes a problem of large volume. In the scheme, the content in the Dockerfile is subjected to a staged naming design. The first stage is used as a code compiling stage, and source codes are compiled into products; and in the second stage, the product is acquired through the name of the first stage to complete the construction of the mirror image. In the first stage, the code compiling environment and the product exist temporarily, and after the product is acquired in the second stage, the compiling environment and the product can be automatically cleaned. When the compilation environment and the artifact are cleaned, the mirror volume is naturally compressed.
For the problem of pulling a code through an SSH protocol in a private code library, in this embodiment, in the first stage of the Dockerfile, the private code library public and private keys are temporarily mounted using SSH type mounting, and after the code is pulled down and compiled successfully, the SSH public and private keys are automatically cleared.
For the problem of when the source code is pulled, in this embodiment, a certificate for pulling the code is obtained in a manner of temporarily mounting a public key and a private key in a Dockerfile, so that the source code is pulled in the Dockerfile.
By combining the above contents, a reasonable Dockerfile which can realize automatic source code pulling in the Dockerfile and reduce the mirror volume can be determined.
However, the Dockerfile file cannot realize the automatic construction of the image, and an open source image construction tool Kaniko launched by Google is needed, the operation of the open source image construction tool Kaniko is not dependent on the Docker daemon process of the node, and therefore the container image can be constructed in the environment without root access authority more easily and safely, such as a Kubernetes cluster.
By using Kaniko, manual intervention is not needed in the whole mirror image construction process, a Docker file path, a mirror image pushing address and a source code position are appointed to an executable program execotor of Kaniko, the execotor can automatically extract the content in Docker file to serve as a file system of a container, then the mirror image construction is automatically realized, and the mirror image is correctly pushed to an appointed warehouse address and cached for subsequent construction.
Specifically, Kaniko can use the cache to cache the mirror layer to the file by setting the cache parameter to true. By default is cached to/in cache. The target file can be modified by the cache-dir parameter. And finally, caching the mirror image layer to a warehouse, wherein the default condition is that the mirror image layer is cached to the address of the final mirror image push warehouse, namely the value specified by the destination parameter. The target warehouse address can be modified by the cache-replay parameter.
The Kaniko working principle is as follows: reading a specified Dockerfile file; extracting the base image specified in the Dockerfile (the image specified in FROM) into the container's file system; each instruction in the Dockerfile is operated respectively; and acquiring a file system snapshot after each operation. The snapshot is created in user space, the file system is traversed and compared to previous states stored in memory; any modification to the file system is added as a new layer to the base image and the image metadata of the image is modified accordingly; and after each Dockerfile instruction is executed, pushing the newly constructed mirror image layer to a specified mirror image warehouse.
By adopting the technical scheme of the embodiment, the mirror image volume can be effectively controlled, the safety of the private code base is ensured, the mirror image construction time is saved, and the source code pulling and compiling, mirror image construction, pushing and caching integration can be realized. Compared with the DinD scheme, in the whole construction process, the CPU utilization rate of the scheme is reduced by 90%, the memory utilization rate is reduced by 81%, and the construction time (for global secondary construction) is shortened by 57%, as shown in fig. 2 to 4. Compared with the DinD scheme, the Kaniko scheme can improve user experience in the aspects of saving computing resources, shortening construction time, improving host machine safety and the like.
The embodiment also discloses a mirror image construction system based on Kubernetes, which is characterized in that: it includes:
the Dockerfile preparation module is used for preparing Dockerfile, mounting a public key and a private key of a private code library, cloning a source code to a specified directory, executing source code compiling to obtain a product, and copying the generated product to make a final mirror image;
and the mirror image manufacturing module is used for analyzing the prepared Dockerfile, executing mirror image construction, caching a mirror image layer, deleting a basic mirror image and pushing the basic mirror image to a mirror image warehouse.
Further, the Dockerfile preparation module comprises a naming module for naming the contents of the code compiling stage in the code compiling stage, acquiring the product by acquiring the naming of the contents of the code compiling stage in the mirror image constructing stage, completing the construction of the mirror image, and then renaming;
the cleaning module is used for deleting the compiling environment and the product in the compiling stage after the product is obtained;
the code pulling module is used for temporarily mounting the public and private keys of the private code library by using SSH type mounting in a code compiling stage and obtaining a certificate of a pulling code, the private code library pulls the code in Dockerfile through an SSH protocol, and after the code is successfully pulled and compiled, the SSH public and private keys are automatically cleaned;
the mirror image manufacturing module comprises an open source mirror image construction tool Kaniko used for constructing mirror images.
The mirror image making module comprises a mirror image construction module, and is used for appointing a Dockerfile path, a mirror image pushing address and a source code position for an executable program execotr of Kaniko, the executable program execotr automatically extracts the content in Dockerfile as a file system of a container, then automatically completes construction of a mirror image, and pushes the mirror image to a specified warehouse address and caches the mirror image for subsequent construction.
The present embodiment also discloses a computer-readable storage medium including a computer program which, when run on a computer, executes the kubernets-based image construction method as described above.
The embodiment also discloses a device, which comprises a processor and a memory which are connected, wherein the processor is used for executing the computer program stored in the memory so as to execute the Kubernetes-based image construction method.
The foregoing is a more detailed description of the invention in connection with specific preferred embodiments and it is not intended that the invention be limited to these specific details. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (10)
1. A mirror image construction method based on Kubernetes is characterized in that: which comprises the following steps:
preparing Dockerfile, mounting a public key and a private key of a private code library, cloning a source code to a specified directory, executing source code compiling to obtain a product, and copying the generated product to make a final mirror image;
and (4) mirror image manufacturing, namely analyzing the prepared Dockerfile, executing mirror image construction, caching a mirror image layer, deleting a basic mirror image, and pushing the basic mirror image to a mirror image warehouse.
2. A mirror image construction method based on kubernets according to claim 1, characterized in that: the preparation of the Dockerfile comprises a code compiling stage and a mirror image constructing stage, and in the preparation process of the Dockerfile, contents in the Dockerfile are named in stages;
in the code compiling stage, naming the content of the code compiling stage; in the mirror image construction stage, the product is obtained by naming the content in the code compiling stage, mirror image construction is completed, and renaming is carried out; and after the product is obtained, deleting the compiling environment and the product in the compiling stage.
3. A mirror image construction method based on kubernets according to claim 2, characterized in that: and in the code compiling stage, the SSH type mounting is used for temporarily mounting the public and private keys of the private code library, the private code library pulls the codes through an SSH protocol, and after the codes are pulled down and compiled successfully, the SSH public and private keys are automatically cleared.
4. A mirror image construction method based on Kubernets according to claim 3, characterized in that: and obtaining a code pulling certificate in a mode of temporarily mounting a public key and a private key in the Dockerfile, wherein the private code library pulls the source code in the Dockerfile.
5. A mirror image construction method based on Kubernets according to claim 4, characterized in that: in the mirror image construction stage, an open source mirror image construction tool Kaniko is adopted to construct a mirror image, and the mirror image construction comprises the following steps:
the method comprises the steps of assigning a Docker file path, a mirror image pushing address and a source code position to an executable program execotr of Kaniko, automatically extracting contents in the Docker file by the executable program execotr to serve as a file system of a container, then automatically completing construction of a mirror image, and pushing the mirror image to an assigned warehouse address and caching the mirror image for subsequent construction.
6. A mirror image construction system based on Kubernetes is characterized in that: it includes:
the Dockerfile preparation module is used for preparing Dockerfile, mounting a public key and a private key of a private code library, cloning a source code to a specified directory, executing source code compiling to obtain a product, and copying the generated product to make a final mirror image;
and the mirror image manufacturing module is used for analyzing the prepared Dockerfile, executing mirror image construction, caching a mirror image layer, deleting a basic mirror image and pushing the basic mirror image to a mirror image warehouse.
7. The Kubernetes-based image construction system according to claim 6, wherein: the Dockerfile preparation module comprises a naming module, which is used for naming the content of the code compiling stage in the code compiling stage, acquiring the product by acquiring the naming of the content of the code compiling stage in the mirror image construction stage, completing the construction of the mirror image and then renaming;
the cleaning module is used for deleting the compiling environment and the product in the compiling stage after the product is obtained;
the code pulling module is used for temporarily mounting the public and private keys of the private code library by using SSH type mounting in a code compiling stage and obtaining a certificate of a pulling code, the private code library pulls the code in Dockerfile through an SSH protocol, and after the code is successfully pulled and compiled, the SSH public and private keys are automatically cleaned;
the mirror image manufacturing module comprises an open source mirror image construction tool Kaniko used for constructing mirror images.
8. The kubernets-based image construction system according to claim 7, wherein:
the mirror image making module comprises a mirror image construction module, and is used for appointing a Dockerfile path, a mirror image pushing address and a source code position for an executable program execotr of Kaniko, the executable program execotr automatically extracts the content in Dockerfile as a file system of a container, then automatically completes construction of a mirror image, and pushes the mirror image to a specified warehouse address and caches the mirror image for subsequent construction.
9. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a computer program which, when run on a computer, performs the kubernets-based image construction method according to any one of claims 1 to 5.
10. An apparatus comprising a processor and a memory coupled together, wherein the processor is configured to execute a computer program stored in the memory to perform the kubernets-based image construction method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110056693.6A CN112835594A (en) | 2021-01-15 | 2021-01-15 | Mirror image construction method and system based on Kubernetes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110056693.6A CN112835594A (en) | 2021-01-15 | 2021-01-15 | Mirror image construction method and system based on Kubernetes |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112835594A true CN112835594A (en) | 2021-05-25 |
Family
ID=75928392
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110056693.6A Pending CN112835594A (en) | 2021-01-15 | 2021-01-15 | Mirror image construction method and system based on Kubernetes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112835594A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113821228A (en) * | 2021-09-30 | 2021-12-21 | 奥特酷智能科技(南京)有限公司 | Method for building ROS or ROS-like project based on layered container mirror image |
| CN115268909A (en) * | 2022-07-23 | 2022-11-01 | 杭州沧浪健康管理有限公司 | Method, system and terminal for establishing and running construction task at web front end |
| CN116301950A (en) * | 2023-05-15 | 2023-06-23 | 北京中诺链捷数字科技有限公司 | Docker image generation method, device, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180123928A1 (en) * | 2015-04-01 | 2018-05-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and devices for monitoring of network performance for container virtualization |
| CN108415795A (en) * | 2018-02-12 | 2018-08-17 | 人和未来生物科技（长沙）有限公司 | A kind of container Dockerfile, container mirror image rapid generation and system |
| CN111198744A (en) * | 2018-11-16 | 2020-05-26 | 中标软件有限公司 | Method for automatic application program containerization and mirror image backup release |
-
2021
- 2021-01-15 CN CN202110056693.6A patent/CN112835594A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180123928A1 (en) * | 2015-04-01 | 2018-05-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and devices for monitoring of network performance for container virtualization |
| CN108415795A (en) * | 2018-02-12 | 2018-08-17 | 人和未来生物科技（长沙）有限公司 | A kind of container Dockerfile, container mirror image rapid generation and system |
| CN111198744A (en) * | 2018-11-16 | 2020-05-26 | 中标软件有限公司 | Method for automatic application program containerization and mirror image backup release |
Non-Patent Citations (3)
| Title |
|---|
| DOCKER_: "利用Kaniko构建容器镜像", pages 1 - 5, Retrieved from the Internet <URL:https://blog.csdn.net/M2l0ZgSsVc7r69eFdTj/article/details/108570585> * |
| 企业运维实践 / DOCKER: "4.Docker容器学习之Dockerfile入门到放弃", pages 1 - 42, Retrieved from the Internet <URL:https://www.cnblogs.com/WeiyiGeek/p/13788496.html> * |
| 死磕音视频: "如何在Dockerfile中clone 私库", pages 1 - 5, Retrieved from the Internet <URL:https://blog.csdn.net/qq_28880087/article/details/110441110> * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113821228A (en) * | 2021-09-30 | 2021-12-21 | 奥特酷智能科技(南京)有限公司 | Method for building ROS or ROS-like project based on layered container mirror image |
| CN115268909A (en) * | 2022-07-23 | 2022-11-01 | 杭州沧浪健康管理有限公司 | Method, system and terminal for establishing and running construction task at web front end |
| CN116301950A (en) * | 2023-05-15 | 2023-06-23 | 北京中诺链捷数字科技有限公司 | Docker image generation method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112835594A (en) | Mirror image construction method and system based on Kubernetes | |
| US10972367B2 (en) | Provisioning framework for binding related cloud services | |
| EP3518098B1 (en) | Cross platform content management and distribution system | |
| KR102010508B1 (en) | System and method for updating source code files | |
| CN102402446B (en) | Method and device for installing application software | |
| US8738883B2 (en) | Snapshot creation from block lists | |
| US10225140B2 (en) | Portable instance provisioning framework for cloud services | |
| US10922123B2 (en) | Container migration in computing systems | |
| US9535729B2 (en) | Live application mobility from one operating system level to an updated operating system level and applying overlay files to the updated operating system | |
| US8893272B2 (en) | Method and device for recombining runtime instruction | |
| US9900324B1 (en) | System to discover and analyze evasive malware | |
| US9513762B1 (en) | Static content updates | |
| US20180143814A1 (en) | Machine-based normalization of machine instructions | |
| US9940461B2 (en) | Enabling an external operating system to access encrypted data units of a data storage system | |
| KR102128472B1 (en) | Storage device for performing in-storage computing operations, method thereof, and system including same | |
| US9501591B2 (en) | Dynamically modifiable component model | |
| US10891114B2 (en) | Interpreter for interpreting a data model algorithm and creating a data schema | |
| WO2017020460A1 (en) | Method and apparatus for integrating plugin | |
| US9652260B2 (en) | Scriptable hierarchical emulation engine | |
| US9292318B2 (en) | Initiating software applications requiring different processor architectures in respective isolated execution environment of an operating system | |
| US20210271458A1 (en) | Managing an app method and system | |
| CN114389936A (en) | Cross-cloud multi-cluster deployment operation and maintenance method, system, processor and storage medium | |
| CN112052459A (en) | Code virtualization encryption method, terminal and storage medium | |
| US10359998B2 (en) | Runstream generator | |
| US20140282516A1 (en) | Providing execution access to files not installed in a virtualized space |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |