Customized container engine, methods, host machine, and media
By integrating traditional container engines into a single-process model and using function call communication, the resource consumption and complexity issues of traditional container engines are resolved, achieving more efficient and reliable container management.
Patent Information
- Application Number
- CN202310151941.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-02-22
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-02-22
AI Technical Summary
Traditional container engines have issues with resource consumption and complexity, especially in embedded environments where unnecessary components consume resources and communication is unreliable.
Design a customized container engine that adopts a single-process model, integrating the dockerd, containerd, and shim processes into a single target daemon process, and achieving inter-process communication through function calls. The functional modules can be flexibly tailored to adapt to different business scenarios.
It reduces resource consumption, improves communication reliability and container engine flexibility, making it suitable for resource-constrained embedded environments.
Smart Images

Figure CN118535273B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of container technology, and in particular to a customized container engine, a container engine configuration method, a container startup method, a host machine, and a computer-readable storage medium. Background Technology
[0002] With the increasing popularity of microservice architecture in software design, more and more containers are being used as the infrastructure to host applications, and microservices have become deeply dependent on containerization technology.
[0003] In traditional container engines, specifically those based on the Docker architecture (a lightweight "virtual machine" used as an open platform for developing, delivering, and running applications), traditional Docker engines, besides container and image lifecycle-related functions, also include other less frequently used or even unused features, such as SwarmKit (a Docker cluster management and container orchestration tool), BuildKit (an image building tool), and even Network (a network management module) and Volume (a volume management module). For example, in some embedded single-board environments for wireless base stations, the Network does not use the default network provided by the Docker engine. The network is customized and planned by the application itself according to its needs, and network management is performed directly in the container network namespace after the application container starts. However, traditional Docker engines still run unnecessary components such as the network during startup or when application containers are created, thus consuming additional resources. Summary of the Invention
[0004] The main purpose of this application is to provide a customized container engine, a container engine configuration method, a container startup method, a host machine, and a computer-readable storage medium, aiming to solve the technical problems of complex and resource-intensive container engines in conventional technologies.
[0005] To achieve the above objectives, this application provides a customized container engine, the customized container engine comprising: The core functional modules include an interface server submodule, a container lifecycle submodule, and an image lifecycle submodule. Optional functional modules, which include configurable selectable sub-modules.
[0006] For example, the customized container engine consists of a target daemon process, in which the dockerd process, containerd process, and shim process are integrated. The functions of each integrated process are implemented in the target daemon process through function calls.
[0007] This application also provides a method for configuring a container engine, which is applied to the customized container engine described above, and the method includes: Based on the business scenario configuration, select the optional sub-module from the optional functional modules to obtain the customized container engine.
[0008] This application also provides a container startup method, which is applied to the customized container engine described above, and the method includes: The interface server submodule receives the startup request for starting the container and creates a container function based on the startup request. The business container corresponding to the startup request is started by calling the container function.
[0009] This application also provides a host machine, the host machine including: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the computer program is executed by the processor, it implements the steps of the container engine configuration method as described above, and the steps of the container startup method as described above.
[0010] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the container engine configuration method and the container startup method as described above.
[0011] This application also provides a configuration apparatus for a container engine, the apparatus being applied to a customized container engine as described above, the apparatus comprising: A customization module is used to select the optional sub-modules among the optional functional modules according to the business scenario configuration, thereby obtaining the customized container engine.
[0012] This application also provides a container startup apparatus, which is applied to the customized container engine described above, and the apparatus includes: A creation module is used to receive a startup request for starting a container through the interface server submodule, and to create a container function based on the startup request; The calling module is used to start the business container corresponding to the startup request by calling the container function.
[0013] This application provides a customized container engine, a configuration method for the container engine, a container startup method, a host machine, and a computer-readable storage medium. The customized container engine includes: a core functional module, which includes an interface server submodule, a container lifecycle submodule, and an image lifecycle submodule; and optional functional modules, which include configurable selectable submodules. The customized container engine is obtained by configuring and selecting the optional submodules from the optional functional modules according to the business scenario.
[0014] The customized container engine consists of a target daemon process, which integrates the dockerd, containerd, and shim processes. Function calls are used within the target daemon process to implement the functionalities of each integrated process. The interface server submodule receives container startup requests and creates container functions based on these requests; the corresponding business container is then started by calling the container functions.
[0015] This application provides a lightweight, novel, and customizable container engine that manages container and image lifecycles by launching a single target daemon process. Compared to traditional Docker containers, the customizable container engine is more suitable for resource-constrained embedded environments: Firstly, compared to traditional container engines, the customizable engine can flexibly tailor functional modules according to different business scenarios, thereby minimizing the complexity of the container engine itself and reducing resource consumption. Secondly, traditional containers require the cooperation of dockerd, containerd, and shim processes to manage container and image lifecycles. The customizable container engine, however, consists of only a single running daemon process; that is, a single-process container engine can accomplish the functions required by multiple processes in a traditional container engine. Compared to multi-process container engines, the customizable container engine consumes fewer resources and is more reliable. Attached Figure Description
[0016] Figure 1 This is a schematic diagram of the structure of the operating device of the hardware operating environment involved in the embodiments of this application; Figure 2 This is a schematic diagram of a container system architecture; Figure 3 This is a schematic diagram of a traditional multi-process container engine; Figure 4 This is a schematic diagram of a single-process container engine representing an embodiment of the communication method between a container engine user and a container involved in the embodiments of this application. Figure 5This is a schematic diagram illustrating the configurable functionality of a container engine, representing an embodiment of a communication method between a container engine user and a container as described in this application. Figure 6 This is a schematic diagram illustrating the configurable functionality of a container engine, representing another embodiment of the communication method between a container engine user and a container involved in the embodiments of this application. Figure 7 This is a comparative schematic diagram of the container startup process under a multi-process engine and a single-process engine in one embodiment of the communication method between the container engine user and the container involved in the embodiments of this application. Figure 8 This is a schematic diagram of a container engine configuration device involved in the embodiments of this application; Figure 9 This is a schematic diagram of the container startup device involved in the embodiments of this application.
[0017] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0018] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.
[0019] Reference Figure 1 , Figure 1 This is a schematic diagram of the operating device structure of the hardware operating environment involved in the embodiments of this application.
[0020] like Figure 1 As shown, the operating device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM), such as a disk drive. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.
[0021] Those skilled in the art will understand that Figure 1The structure shown does not constitute a limitation on the operating equipment and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0022] like Figure 1 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a data storage module, a network communication module, a user interface module, and computer programs.
[0023] exist Figure 1 In the illustrated operating device, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with the user; the processor 1001 and memory 1005 in the operating device of this application can be disposed in the operating device, and the operating device calls the computer program stored in the memory 1005 through the processor 1001 and performs the following operations: Based on the business scenario configuration, select the optional sub-module from the optional functional modules to obtain the customized container engine.
[0024] In one embodiment, the processor 1001 may invoke a computer program stored in the memory 1005 and further perform the following operations: The step of selecting the optional sub-module from the optional functional modules according to the business scenario configuration to obtain the customized container engine includes: Before compiling the container engine, the customized container engine is generated based on the core functional modules and the selected optional sub-modules.
[0025] In one embodiment, the processor 1001 may invoke a computer program stored in the memory 1005 and further perform the following operations: The step of selecting the optional sub-module from the optional functional modules according to the business scenario configuration to obtain the customized container engine further includes: After the customized container engine is started, the selected optional submodules are dynamically loaded into the customized container engine, or the selected optional submodules in the customized container engine are unloaded to generate a new customized container engine.
[0026] In one embodiment, the processor 1001 may invoke a computer program stored in the memory 1005 and further perform the following operations: The interface server submodule receives the startup request for starting the container and creates a container function based on the startup request. The business container corresponding to the startup request is started by calling the container function.
[0027] In one embodiment, the processor 1001 may invoke a computer program stored in the memory 1005 and further perform the following operations: The step of starting the business container corresponding to the startup request by calling the container function includes: If the local image does not exist, drag the container image from the image repository as the local image; After the local image is ready, the container function is called to generate the running command for the local image, and the business container corresponding to the startup request is started based on the running command.
[0028] In the field of container technology, an engine is a tool for creating and managing containers. It generates containers by reading images and is responsible for pulling images from or submitting images to a repository. An image is similar to a virtual machine image, generally consisting of a basic operating system environment and multiple applications packaged together, serving as a template for creating containers. A container can be viewed as a simplified Linux system environment (including root user privileges, process space, user space, and network space) and the applications running within it, packaged together as a box. A repository is a centralized place for storing image files, divided into public repositories and private repositories. Currently, the largest public repository is the official Docker Hub, and domestic cloud providers such as Alibaba Cloud and Tencent Cloud also provide public repositories. A host machine is the server where the operating system running the engine resides.
[0029] Reference Figure 2 Docker images: a unified packaging method -> templates; Docker containers: a unified runtime environment -> based on images, with runtime status; Docker registry: an image repository: a repository for storing images -> storing image templates. 1. The client initiates various commands to the host (DOCKER_HOST); 2. The host will access the image; if the image is available, it will be used directly and run as a container; 3. If the image is not available in the registry, it will be pulled from the public registry, added to the local machine, and then run as a container.
[0030] The container engine is the foundation for managing and running containers, see reference... Figure 3The traditional container engine, Docker, has the following architecture: The main components of the Docker engine are the Docker client, the Docker daemon, the containerd process, and the runc process. They are jointly responsible for the creation and execution of containers. Inter-process communication between the Docker client and the Docker daemon, between the Docker daemon and the containerd process, and between the containerd process and the shim process is achieved through gRPC (gRPC Emote Procedure Calls, an open-source remote procedure call system initiated by Google).
[0031] First, under high gRPC pressure or system load, the reliability of gRPC communication will inevitably be affected, thus impacting the robustness of the Docker engine. Furthermore, the presence of gRPC clients and servers within the processes, with the server being a simplified version of an HTTP server (web server), leads to significant resource consumption for inter-process gRPC communication. Additionally, direct inter-process communication creates a long-lived gRPC connection, which also consumes substantial resources. Moreover, this multi-process model requires more computational and memory resources, making it unsuitable for resource-constrained embedded systems such as IoT, wearable devices, and smart meters.
[0032] Second, in addition to container and image lifecycle-related functions, traditional Docker engines also include other less frequently used or even unused functions, such as SwarmKit (a Docker cluster management and container orchestration tool), BuildKit (an image building tool), and even Network (a network management module) and Volume (a volume management module). For example, in some embedded single-board environments for wireless base stations, the Network does not use the default network provided by the Docker engine. The network is customized and planned by the application itself according to its needs, and network management is performed directly in the container network namespace after the application container starts. However, traditional Docker engines still run unnecessary components such as the network when starting up or when application containers are created, thus consuming additional resources.
[0033] In summary, this application redesigns the container engine to reduce its resource consumption and improve communication efficiency between users and containers, thereby making communication between container engine users and containers more reliable.
[0034] Correspondingly, firstly, compared to traditional container engines, the novel container engine provided in this application can flexibly tailor functional modules according to different business scenarios, thereby minimizing the complexity of the container engine itself and reducing its resource consumption. The container engine offers flexible function selection and can be configured and tailored according to different scenarios, reducing the size of the container engine program itself and achieving the goal of saving system resources.
[0035] Secondly, traditional containers require the coordinated operation of dockerd, containerd, and shim processes to manage the container and image lifecycles. In contrast, the novel container engine provided in this application consists of only a single running daemon process; this single-process container engine can accomplish the functions that traditional container engines require multiple processes working together. Compared to multi-process container engines, this new container engine consumes fewer resources and is more reliable. Compared to traditional open-source container engines, this new container engine requires fewer processes and less hardware resources (such as memory and CPU), resulting in greater cost savings.
[0036] This application provides a customized container engine. In one embodiment of the customized container engine, the customized container engine includes: The core functional modules include an interface server submodule, a container lifecycle submodule, and an image lifecycle submodule. Optional functional modules, which include configurable selectable sub-modules.
[0037] Reference Figure 4 In this embodiment, a lightweight, novel, and customized container engine is designed. This customized container engine has the following characteristics: it provides smaller core functional modules, which only include two main parts: container lifecycle and image lifecycle. The container engine provides services externally using an API server, creating containers and images that conform to the OCI (Open Container Initiative) standard.
[0038] This new type of container engine allows for the configurable removal of other non-core functional modules. By configuring optional functional modules according to business scenarios, a customized container engine can be created, and containers can be maintained based on this customized engine. This not only makes the container engine's functional configuration more flexible but also makes it more lightweight.
[0039] This new container engine can be used in all operating system environments (including but not limited to MACOS, LINUX / UNIX, Windows, VxWorks, uCOS, etc.), as well as in server operating systems and embedded operating systems.
[0040] In another embodiment of the customized container engine in this application, the customized container engine consists of a target daemon process, in which the dockerd process, containerd process, and shim process are integrated, and the functions of each integrated process are implemented by function calls in the target daemon process.
[0041] Reference Figure 4 In the customized container engine proposed in this application, the container engine is designed as a single-process model, consisting of a single target daemon process. Compared to the traditional Docker engine, this integrates the dockerd process, containerd process, and shim process into a single process. Furthermore, the functionality of each integrated process is implemented by the target daemon process through function calls.
[0042] For example, the processes integrated in the target daemon include the dockerd process, the containerd process, and the shim process; Alternatively, it could include the dockerd process and the containerd process; Alternatively, it could include the containerd process and the shim process.
[0043] In one embodiment, the processes integrated in the target daemon process can be the dockerd process, the containerd process, and the shim process, all combined into one; however, it is not limited to a three-in-one combination, it can also be the dockerd process and the containerd process, combined into one; or the containerd process and the shim process, combined into one. This allows for flexible and efficient integration of processes to obtain the target daemon process.
[0044] thereby: 1) The communication between processes has been changed from gRPC to function call communication between the traditional container processes (dockerd, containerd, and shim). Under high system load, gRPC communication can severely impact message exchange, potentially causing container failures. Consolidating multiple processes into a single process and allowing direct function call communication improves reliability, eliminating the need for a gRPC server (and thus an HTTP / Web server), saving resources and resolving the issue of gRPC communication failures under high load. 2) Merging multiple processes into one reduces the number of processes and resource consumption. This reduced resource consumption makes communication between the container engine user and the container more reliable.
[0045] In one application scenario, to achieve high reliability of communication between the components of the container engine and reduce the number of processes of the container engine itself, the functions of container creation, startup, stop, and deletion, which previously required the cooperation of the dockerd process, containerd process, and shim process, are implemented in a single process through function calls, thereby combining the three types of processes, dockerd process, containerd process, and shim process, into one.
[0046] This application provides a method for configuring a container engine, which is applied to the customized container engine described above. The method includes: Based on the business scenario configuration, select the optional sub-module from the optional functional modules to obtain the customized container engine.
[0047] For configurable implementations of container engines, the core functional modules of the container are mandatory, mainly consisting of the apiserver, container lifecycle, and image lifecycle functionalities. Other optional modules include swarmkit, buildkit, network, and volume. Customized container engines are obtained by selecting optional sub-modules from these modules based on the business scenario.
[0048] For example, the step of selecting the optional sub-module among the optional functional modules according to the business scenario configuration to obtain the customized container engine includes: Before compiling the container engine, the customized container engine is generated based on the core functional modules and the selected optional sub-modules.
[0049] Reference Figure 5Before compilation, the required functional modules can be selected through a graphical configuration menu or configuration file, allowing for the removal of unnecessary and redundant features and flexible configuration options for the container engine. After compilation, this effectively reduces the complexity and resource overhead of the container engine executable itself. In one embodiment, the specific implementation steps for obtaining a customized container engine are as follows: (1) Analyze business scenario requirements and perform analysis for customized container engines.
[0050] (2) Freely select the required engine functions and trim the functional modules through the configuration menu (graphical configuration menu or configuration file).
[0051] (3) Compile the trimmed container engine and generate its executable program.
[0052] (4) Run the container engine.
[0053] For example, the step of selecting the optional sub-module among the optional functional modules according to the business scenario configuration to obtain the customized container engine includes: Before compiling the container engine, the customized container engine is generated based on the core functional modules and the selected optional sub-modules.
[0054] Reference Figure 6 Alternatively, the container engine's functionality can be minimized initially, ensuring only essential container and image lifecycle functions are maintained. Once the container engine is running, other optional modules can be dynamically loaded into the container engine process as plugins, or their corresponding functions can be uninstalled from the container engine. This also achieves the goal of flexibly tailoring the container engine. In one embodiment, the specific implementation steps for obtaining a customized container engine are as follows: (1) Compile the container engine core module to generate a minimal executable program.
[0055] (2) Start the minimum executable container engine program.
[0056] (3) Dynamically select other optional functional modules of the container engine to compile based on business needs.
[0057] (4) Load the compiled optional modules into the running process.
[0058] (5) The optional container engine function can be launched and used.
[0059] (6) When optional functions are not needed, they can be dynamically unloaded from the container engine main process according to requirements, reducing engine resource consumption.
[0060] This application provides a container startup method, which is applied to the customized container engine described above. The method includes: The interface server submodule receives the startup request for starting the container and creates a container function based on the startup request. The business container corresponding to the startup request is started by calling the container function.
[0061] After the interface server submodule receives a user's request to start a container, it creates a container function based on the request and starts the corresponding business container by calling the container function. Thus, communication between processes is achieved directly through function calls, and the functionality of each process integrated within the target daemon is implemented through function calls within the target daemon.
[0062] For example, the step of starting the business container corresponding to the startup request by calling the container function includes: If the local image does not exist, drag the container image from the image repository as the local image; After the local image is ready, the container function is called to generate the running command for the local image, and the business container corresponding to the startup request is started based on the running command.
[0063] The client sends various commands to the host; the host then uses the local image. If a local image exists, it is used directly and run as a container; otherwise, it pulls the image from the registry, adds it to the local machine, and runs it as a container. Once the local image is ready, the host generates the run command for the local image by calling container functions, and starts the corresponding business container based on the run command.
[0064] In one application scenario, refer to Figure 7 The process of starting a container under a single-process container engine is as follows: 1. The user initiates a request to start the container; 2. When a single-process container receives a request to create a container, the engine's own API server processes the request, parses the parameters, and forwards it to the backend to start a new coroutine to define the container creation function. 3. Create a container function, which creates a container object based on the request parameters and saves the object information to the database. Then, call the container startup function. 4. The container startup function implements the actual startup of the container. When starting the container, it first checks whether the local image exists. If it does not exist, it drags the container image from the remote image repository. 5. Once the image resources are ready, directly call the runtime command to start the main process of the business container, and the business container will then be running.
[0065] In addition, refer to Figure 8 This application also provides a container engine configuration apparatus, which is applied to the customized container engine described above. The apparatus includes: The custom module M1 is used to select the optional sub-module among the optional functional modules according to the business scenario configuration to obtain the customized container engine.
[0066] For example, the configuration device of the container engine is further used for: Before compiling the container engine, the customized container engine is generated based on the core functional modules and the selected optional sub-modules.
[0067] For example, the configuration device of the container engine is further used for: After the customized container engine is started, the selected optional submodules are dynamically loaded into the customized container engine, or the selected optional submodules in the customized container engine are unloaded to generate a new customized container engine.
[0068] Reference Figure 9 This application also provides a container startup apparatus, which is applied to the customized container engine described above, and the apparatus includes: Create module N1, which is used to receive the startup request of the container through the interface server submodule and create a container function based on the startup request; Module N2 is invoked to start the business container corresponding to the startup request by invoking the container function.
[0069] For example, the calling module is also used to: If the local image does not exist, drag the container image from the image repository as the local image; After the local image is ready, the container function is called to generate the running command for the local image, and the business container corresponding to the startup request is started based on the running command.
[0070] The container engine configuration device and container startup device provided in this application respectively adopt the container engine configuration method and container startup method in the above embodiments, solving the technical problems of complex and resource-intensive container engines in conventional technology. Compared with conventional technology, the beneficial effects of the container engine configuration device and container startup device provided in this application are the same as the beneficial effects of the container engine configuration method and container startup method provided in the above embodiments, and other technical features in the container engine configuration device and container startup device are the same as the features disclosed in the methods of the above embodiments, and will not be repeated here.
[0071] Furthermore, this application embodiment also provides a host machine, the host machine including: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the computer program is executed by the processor, it implements the steps of the container engine configuration method as described above, and the steps of the container startup method as described above.
[0072] Furthermore, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the container engine configuration method and the steps of the container startup method as described above.
[0073] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.
[0074] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to conventional technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0075] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A customized container engine, characterized by, The customized container engine consists of a target daemon process, and implements the functions of each integrated process within the target daemon process through function calls. The customized container engine includes: The core functional modules include an interface server submodule, a container lifecycle submodule, and an image lifecycle submodule. Optional functional modules, which include configurable selectable sub-modules; The processes integrated in the target daemon include the dockerd process, the containerd process, and the shim process; Alternatively, it could include the dockerd process and the containerd process; Alternatively, it could include the containerd process and the shim process.
2. A method of configuring a container engine, the method comprising: The method is applied to the customized container engine as described in claim 1, and the method includes: Based on the business scenario configuration, select the optional sub-module from the optional functional modules to obtain the customized container engine.
3. The method of configuring a container engine of claim 2, wherein, The step of selecting the optional sub-module from the optional functional modules according to the business scenario configuration to obtain the customized container engine includes: Before compiling the container engine, the customized container engine is generated based on the core functional modules and the selected optional sub-modules.
4. The container engine configuration method as described in claim 2, characterized in that, The step of selecting the optional sub-module from the optional functional modules according to the business scenario configuration to obtain the customized container engine further includes: After the customized container engine is started, the selected optional submodules are dynamically loaded into the customized container engine, or the selected optional submodules in the customized container engine are unloaded to generate a new customized container engine.
5. A container startup method, characterized in that, The method is applied to the customized container engine as described in claim 1, and the method includes: The interface server submodule receives the startup request for starting the container and creates a container function based on the startup request. The business container corresponding to the startup request is started by calling the container function.
6. The container startup method as described in claim 5, characterized in that, The step of starting the business container corresponding to the startup request by calling the container function includes: If the local image does not exist, drag the container image from the image repository as the local image; After the local image is ready, the container function is called to generate the running command for the local image, and the business container corresponding to the startup request is started based on the running command.
7. A host machine, characterized in that, The host machine includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the container engine configuration method as described in any one of claims 2 to 4, and the steps of the container startup method as described in any one of claims 5 to 6.
8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the container engine configuration method as described in any one of claims 2 to 4, and the steps of the container startup method as described in any one of claims 5 to 6.
Citation Information
Patent Citations
Service container engine
CN103942052A
Container creation method and device, electronic equipment and computer readable storage medium
CN114840310A
