CN115904623A - Container creation method and system, electronic device, and storage medium - Google Patents
Container creation method and system, electronic device, and storage medium Download PDFInfo
- Publication number
- CN115904623A CN115904623A CN202211504064.6A CN202211504064A CN115904623A CN 115904623 A CN115904623 A CN 115904623A CN 202211504064 A CN202211504064 A CN 202211504064A CN 115904623 A CN115904623 A CN 115904623A
- Authority
- CN
- China
- Prior art keywords
- container
- runtime
- request
- file
- cloud service
- 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
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a container creating method and system, electronic equipment and a storage medium, wherein the container creating method comprises the following steps: the advanced container runtime initiates a container creation request to the cloud service runtime; the cloud service runtime writes container configuration information into a container operation standard file stored in a container subprocess directory file according to the container creation request; and the bottom layer container runtime executes container creation according to the container configuration information. According to the container creating method, the operation field value is configured in the operation of the high-level container by replacing the operation of the bottom-layer container during the operation of the cloud service, so that the special settings of environment variables, pre-starting hook functions, equipment mounting and the like of the container, which accord with a cloud service scene, can be automatically set without manually specifying container starting commands one by one.
Description
Technical Field
The present invention relates to the field of cloud computing technologies, and in particular, to a container creation method and system, an electronic device, and a storage medium.
Background
In the existing container creation process, when configuration information such as device mounting needs to be set, configuration information such as environment variables of all containers needs to be manually set one by one at the beginning of container creation.
Therefore, in order to solve the above technical problems, it is necessary to provide a new container creation method and system.
Disclosure of Invention
The invention aims to provide a container creation method and system, an electronic device and a storage medium, which can automatically set container configuration information in the container creation process.
In order to realize the purpose, the technical scheme provided by the invention is as follows:
in a first aspect, the present invention provides a container creating method, including:
the advanced container runtime initiates a container creation request to the cloud service runtime;
the cloud service runtime writes container configuration information into a container operation standard file stored in a container subprocess directory file according to the container creation request;
and the bottom layer container runtime executes container creation according to the container configuration information.
In one or more embodiments, the writing of the container configuration information into the container operation standard file stored in the container child process directory file includes:
the cloud service runtime decodes the container operation standard file stored in the container sub-process directory file, and writes an equipment mounting file required by a container into the decoded container operation standard file;
and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
In one or more embodiments, the device mount file is an existing device file at the runtime of the cloud service.
In one or more embodiments, the writing of the container configuration information into the container operation standard file stored in the container child process directory file includes:
the cloud service runtime decodes the container operation standard file stored in the container sub-process directory file, and writes an environment variable required by container operation into the decoded container operation standard file;
recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
In one or more embodiments, the writing of the container configuration information into the container operation standard file stored in the container child process directory file includes:
the cloud service runtime decodes the container operation standard file stored in the container subprocess directory file, and writes a hook function required by container operation into the decoded container operation standard file;
recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
In one or more embodiments, the writing, by the cloud service runtime, container configuration information into a container operation standard file according to the container creation request includes:
and the cloud service runtime receives the container creation request, initializes the container, and writes container configuration information into a container operation standard file, wherein the initialization comprises setting a printing path of a system log.
In one or more embodiments, the advanced container runtime initiating a container creation request to a cloud services runtime, comprising:
the advanced container runtime initiates a container creation request to the cloud service runtime in response to the received container runtime request.
In one or more embodiments, the container creation method further includes:
the method comprises the steps that a container operation request initiated by a user is received by a runtime command line interface, and the container operation request is analyzed to generate corresponding request parameters;
the runtime command line interface verifies the request parameters;
when the request parameter checks pass, the runtime command line interface sends the container run request to the advanced container runtime.
In a second aspect, the present invention provides a container creation system, comprising: a premium container runtime, a cloud service runtime, and a bottom container runtime; the advanced container runtime is used for initiating a container creation request to the cloud service runtime; the cloud service runtime is used for writing container configuration information into a container operation standard file stored in a container subprocess directory file according to the container creation request; the bottom layer container runtime is used for executing container creation according to the container configuration information.
In one or more embodiments, the container creation system further includes a runtime command line interface, where the runtime command line interface is configured to receive a container operation request initiated by a user, and parse the container operation request to generate a corresponding request parameter;
the runtime command line interface is further configured to verify the request parameter, and when the request parameter is verified, the runtime command line interface sends the container operation request to the advanced container runtime;
the advanced container runtime is used for initiating the container creation request to the cloud service runtime according to the container operation request.
In a third aspect, the invention provides an electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the container creation method as described in any of the preceding when executing the program.
In a fourth aspect, the invention provides a computer storage medium having stored thereon computer executable instructions for implementing the container creation method as described in any one of the preceding claims when executed by a processor.
Compared with the prior art, the container creating method provided by the invention has the advantages that the operation time field value is configured in the operation time of the high-level container through the operation time of the cloud service instead of the operation time of the bottom-level container, so that the special settings of the environment variable, the pre-starting hook function, the equipment mounting and the like of the container, which accord with the cloud service scene, can be automatically set without manually specifying the container starting commands one by one.
Drawings
FIG. 1 is a flow diagram of a container creation method in one embodiment of the invention;
FIG. 2 is a schematic diagram of a container creation system according to an embodiment of the present invention;
fig. 3 is a block diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
Specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings, but it should be understood that the scope of the present invention is not limited to the specific embodiments.
Throughout the specification and claims, unless explicitly stated otherwise, the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element or component but not the exclusion of any other element or component.
In order to facilitate understanding of the technical aspects of the present application, technical terms that may appear in the present invention are first explained in detail below.
Container (Container) technique: the technology of effectively dividing resources of a single operating system into isolated groups so as to better balance conflicting resource usage requirements among the isolated groups is container technology. Containers created based on container technology, similar to virtual machines, but with relaxed isolation properties, can share the operating system between applications.
Container runtime (container runtime) refers to a series of programs and environments that a container needs to run. For example, it may refer to software that executes containers and manages container images on nodes. The most widely used vessel at present is Docker, and other common vessels include, but are not limited to: rkt, containerd, CRI-O, etc.
A command-line interface (CLI) is an important way for a user to interact with a network device. In this way, if a user needs to perform some processing on the service data of the network device, a corresponding CLI command can be input on the interface, and the network device can present the processing result on the interface after executing the command for the user to view and use.
In a cloud service scenario, a container engine such as Docker or container is generally used as a high-level container runtime, and runc (the most widely used container runtime at present, which is originally developed as a part of Docker, is extracted later as a separate tool and library, and implements a root file system of an OCI specification including config. When configuration information such as device mount of a container needs to be set, it is necessary to specify a start command for the container one by one at the beginning of container creation. The container creation method provided by the invention can realize the appointed setting of the container configuration information such as the equipment mounting of the container and the like based on the cloud service operation in the cloud service scene.
Referring to fig. 1, a container creating method according to an embodiment of the present invention includes the following steps:
s102: the advanced container runtime initiates a container creation request to the cloud service runtime. It should be noted that the High-Level container runtime (High-Level container runtime) includes multiple upper-layer functions such as grpc (open source remote procedure call framework developed by google) call, mirror image storage management, and the like, and is mainly responsible for transmitting and managing container mirror images, decompressing mirror images, and transmitting to the bottom-Level container runtime to run the container. In this embodiment, a container engine such as Docker, container, etc. may be used to run as a high-level container.
The Low-Level container runtime (Low-Level container runtime) refers to a container runtime that only focuses on running a container, which may invoke an operating system, implement resource isolation and restriction using a namespace (namespace) and a control group (cgroup), and focuses mainly on how to interact with operating system resources and create and run the container. In the present embodiment, run, lmctfy, rkt, and the like can be used as the bottom layer container operation.
The cloud service runtime may be a private cloud runtime or a public cloud runtime, and is not particularly limited in this embodiment.
In an exemplary embodiment, the advanced container runtime initiates a container creation request to the cloud services runtime in response to the received container runtime request. Wherein the container operation request received by the advanced container operation is sent by an operation time command line interface. The runtime command line interface may provide for user interaction.
Specifically, the runtime command line interface may receive a container operation request initiated by a user, and parse the container operation request to generate a corresponding request parameter; the runtime command line interface verifies the request parameters; when the request parameter checks pass, the runtime command line interface sends the container run request to the advanced container runtime.
The container operation request comprises information such as a container name, a starting port and a mirror image used by the container.
Further, in the process of analyzing the container operation request by the runtime command line interface, information contained in the container operation request can be converted into corresponding request parameters, and unknown information in the container operation request can be automatically set as default values. For example, when the start port information in the container operation request is unknown, the start port information may be automatically set to a default value.
Further, the checking content of the request parameter specifically includes: whether the format of the request is normal, whether the boot port is duplicated, whether an image exists, etc. When all contents of the request parameters are verified, the runtime command line interface sends the aforementioned container run request to the senior container runtime. Otherwise, the runtime command line interface terminates subsequent operations to send container operation requests.
S104: and writing the container configuration information into the container operation standard file stored in the container subprocess directory file according to the container creation request during the cloud service operation.
It should be noted that, in this embodiment, the cloud server for providing the cloud service environment may be an ARM-based server or an X86-based server, and the operating system running in the cloud server may be a Linux operating system. The cloud server is preferably an ARM chip server, and the ARM chip server includes a CPU, a Mali GPU (Graphics Processing Unit, marlin Graphics processor), and an NIC (Network Interface Controller). Compared with a traditional X86-structured server, the system does not need to integrate an additional GPU chip when the multimedia data are sent to the outside of the container. The ARM chip server runs a Linux operating system, and the parameters of namespace, cgroup, overlayfs, veth and the like of a Linux kernel are configured in the Linux operating system, so that the Linux operating system can support container engines such as Docker and Containerd.
In the container creating process, a directory with the same name is created according to the specified container name, for example, if the container name is DockerA, the created directory is/DockerA. Then the designated container image is run (the container image file is generally a script file describing the steps of creating the root file system), the root file system is created under the container name directory, and the container name directory is set as the container root directory, after which the container run runs with the container name directory as the root directory, and the container child process directory file is stored under the container root directory.
The Container operation standard file is a file that specifies a Container format and an operation standard, and in this embodiment, the Container operation standard file conforms to an OCI (Open Container initiator). The OCI provides two specifications: a mirror specification and a runtime specification. The image specification defines a standard of the OCI image, and after the advanced container runtime downloads an OCI image, the OCI image is decompressed into an OCI runtime file system package (filesystem bundle), for example, an image format and operation are established. The runtime specification describes how to run the container program from the OCI runtime file system package and defines the configuration, runtime environment and lifecycle of the container, and how to set namespaces (namespaces) and control groups (cgroups) for new containers, and mount the root file system, among other operations. Thus, the created container may be made to follow the corresponding container configuration by writing the container configuration information into the container operation standard file.
In an exemplary embodiment, the cloud service runtime receives the container creation request, initializes the container creation request, and writes container configuration information into a container operation standard file. The initialization comprises the step of setting a printing path of a system log so as to conveniently check an error log when the cloud service runs when a fault occurs.
Specifically, after receiving the container creation request during the cloud service operation, the cloud service operation may judge the request type, and after determining that the request type is the container creation request, perform an operation of writing container configuration information into the container operation standard file; otherwise, the subsequent container creation operation is terminated. When the request type is other request types except the container creation request, the container already exists, and other requests triggered by restarting and the like are usually indicated, so that subsequent container creation operation is skipped, and the container can be directly started.
In an exemplary embodiment, writing the container configuration information into the container operation standard file stored in the container sub-process directory file includes: the cloud service runtime decodes the container operation standard file stored in the container sub-process directory file, and writes an equipment mounting file required by a container into the decoded container operation standard file; and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file. The device mount file is an existing device file during the cloud service operation.
Taking Linux system as an example, the process of mounting the file by the device required by the write container is further described as follows: the method comprises the steps that a container operation standard file (an OCI file) is stored in a container sub-process directory file in a Linux system in a Linux file mode, after the container operation standard file is decoded during cloud service operation, existing equipment files (including equipment mounting paths, equipment sources, equipment types and other instructions of character string types) during cloud service operation are automatically written into spec.Mount of the container operation standard file; and after the writing is finished, recoding the container to run the standard file, and flushing the standard file into the container subprocess directory file.
In an exemplary embodiment, writing the container configuration information into the container operation standard file stored in the container child process directory file includes: the cloud service runtime decodes the container operation standard file stored in the container sub-process directory file, and writes an environment variable required by container operation into the decoded container operation standard file; and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
Taking Linux system as an example, the process of writing the environment variables required by the container operation is further described: the method comprises the steps that a container operation standard file (OCI file) is stored in a container sub-process directory file in a Linux system in a Linux file mode, after the container operation standard file is decoded during cloud service operation, environment variables required by container operation are automatically written into spec.process.env of the operation standard file in a linked list structure, and environment variable information is added to the linked list in a key value mode; and after the writing is finished, recoding the container to run the standard file, and flushing the standard file into the container subprocess directory file.
In an exemplary embodiment, writing the container configuration information into the container operation standard file stored in the container child process directory file includes: the cloud service runtime decodes the container operation standard file stored in the container subprocess directory file, and writes a hook function required by container operation into the decoded container operation standard file; and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
Taking Linux system as an example, the process of the hook function required by the operation of the write container is further described as follows: the method comprises the steps that a container operation standard file (an OCI file) is stored in a container subprocess directory file in a Linux system in a Linux file mode, after the container operation standard file is decoded in cloud service operation, a hook function (comprising a function path, an environment variable, calling timeout time, an extra character string type parameter and the like) required by container operation is automatically written into a spec, hooks, prestart of the operation standard file; and after the writing is finished, recoding the container to run the standard file, and flushing the standard file into the container subprocess directory file. The hook function is automatically called after the container start operation command space is created, and the container process can be subjected to more custom operations such as kernel dynamic loading, system function replacement and the like by writing the custom hook function.
The hook function is an executable program, and when a dynamic executable program needs to be loaded, the Linux system loads a shared library required by running the dynamic link executable program through a dynamic loader (dynamic loader). The hook function will write the kernel module path to be loaded in/etc/ld.so.conf and convert it into the ld.so.cache file using the ldconfig command of Linux, so that the dynamic loader can find the required shared library.
The dynamic loader finds a shared library by means of two files/etc/ld.so.conf and/etc/ld.so.cache. Conf file contains a list of all directories (except/lib and/usr/lib) that the dynamic loader will look up in the shared library. But before the dynamic loader can "see" this information, it must be translated into the ld.so. This can be done by running the ldconfig command, which when finished results in a new/etc/ld.so.cache file that can reflect the changes made to/etc/ld.so.that the dynamic loader will look at all the new directories specified in/etc/ld.so.conf when looking for shared libraries.
S106: and the bottom layer container runtime executes container creation according to the container configuration information.
After the writing of the container configuration information in step S104 is completed, the bottom-layer container runtime may execute container creation according to the container configuration information written in the container operation standard file by the cloud service runtime.
In the container creation method provided in this embodiment, the runtime field value is configured in the high-level container runtime through the cloud service runtime instead of the bottom-level container runtime, so that the unique settings conforming to the cloud service scenario, such as the environment variable, the pre-boot hook function, and the device mount of the container, can be automatically set without manually specifying the container start command one by one.
Referring to fig. 2, based on the same inventive concept as the container creation method shown in fig. 1, an embodiment of the present invention further provides a container creation system 200, where the container creation system 200 includes a high-level container runtime 201, a cloud service runtime 202, an underlying container runtime 203, and a runtime command line interface 204.
The runtime command line interface 204 is configured to receive a container operation request initiated by a user, and parse the container operation request to generate corresponding request parameters. The container operation request comprises information such as a container name, a starting port and a mirror image used by the container. The runtime command line interface 204 is further configured to check the request parameter, and when the request parameter passes the check, the runtime command line interface 204 sends the container operation request to the advanced container runtime 201.
Specifically, in the process of analyzing the container operation request, the runtime command line interface 204 can convert information contained in the container operation request into corresponding request parameters, and can automatically set the default value for unknown information in the container operation request.
Further, the checking content of the request parameter specifically includes: whether the format of the request is canonical, whether the boot port is duplicated, whether an image exists, etc. When all the contents of the request parameters are verified, the runtime command line interface 204 sends the aforementioned container run request to the advanced container runtime 201. Otherwise, the runtime command line interface 204 terminates subsequent operations to send container run requests.
The advanced container runtime 201 is configured to initiate a container creation request to the cloud service runtime 202 according to the received container operation request. The high-level container runtime 201 may be a container engine such as Docker, containerd, etc.
In particular, the advanced container runtime 201 initiates a container creation request to the cloud service runtime 202 in response to a received container run request sent by the runtime command line interface 204.
The cloud service runtime 202 is configured to write container configuration information into a container operation standard file stored in the container child process directory file according to the container creation request. The container configuration information comprises a device mount file required by the container, an environment variable required by the container to operate, a hook function required by the container to operate and the like.
Specifically, the cloud service runtime 202 receives a container creation request initiated by the advanced container runtime 201, initializes the container creation request, and writes container configuration information into a container operation standard file. Wherein the initializing includes setting a print path of the system log.
Further, the cloud service runtime 202 decodes the container operation standard file stored in the container sub-process directory file, and writes a device mount file required by the container into the decoded container operation standard file; and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file. The device mount file is an existing device file of the cloud service runtime 202.
Further, the cloud service runtime 202 decodes a container operation standard file stored in the container sub-process directory file, and writes an environment variable required for container operation into the decoded container operation standard file; and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
Further, the cloud service runtime 202 decodes the container operation standard file stored in the container subprocess directory file, and writes a hook function required for container operation into the decoded container operation standard file; recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file. The underlying container runtime 203 is configured to perform container creation according to the container configuration information. The underlying container runtime 203 may be runc, lmctfy, rkt, etc.
Referring to fig. 3, an embodiment of the present invention further provides an electronic device 300, where the electronic device 300 includes at least one processor 301, a storage 302 (e.g., a non-volatile storage), a memory 303, and a communication interface 304, and the at least one processor 301, the storage 302, the memory 303, and the communication interface 304 are connected together via a bus 305. The at least one processor 301 is configured to invoke at least one program instruction stored or encoded in the memory 302 to cause the at least one processor 301 to perform the various operations and functions of the container creation method described in the various embodiments of the present specification.
In embodiments of the present description, the electronic device 300 may include, but is not limited to: personal computers, server computers, workstations, desktop computers, laptop computers, notebook computers, mobile electronic devices, smart phones, tablet computers, cellular phones, personal Digital Assistants (PDAs), handsets, messaging devices, wearable electronic devices, consumer electronic devices, and the like.
Embodiments of the present invention also provide a computer-readable storage medium having stored thereon computer-executable instructions for implementing various operations and functions of the container creation method described in the embodiments of the present specification when executed by a processor.
The computer-readable storage medium can be any available media or data storage device that can be accessed by a computer, including but not limited to magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), solid State Disks (SSDs), etc.).
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing descriptions of specific exemplary embodiments of the present invention have been presented for purposes of illustration and description. It is not intended to limit the invention to the precise form disclosed, and obviously many modifications and variations are possible in light of the above teaching. The exemplary embodiments were chosen and described in order to explain certain principles of the invention and its practical application to enable one skilled in the art to make and use various exemplary embodiments of the invention and various alternatives and modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims and their equivalents.
Claims (12)
1. A method of container creation, comprising:
the advanced container runtime initiates a container creation request to the cloud service runtime;
the cloud service runtime writes container configuration information into a container operation standard file stored in a container subprocess directory file according to the container creation request;
and the bottom layer container runtime executes container creation according to the container configuration information.
2. The container creation method of claim 1, wherein the writing of container configuration information into a container operation standard file stored in a container child process directory file comprises:
the cloud service runtime decodes the container operation standard file stored in the container sub-process directory file, and writes an equipment mounting file required by a container into the decoded container operation standard file;
and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
3. The container creation method of claim 2, wherein the device mount file is an existing device file at the cloud service runtime.
4. The container creation method of claim 1, wherein the writing of the container configuration information into the container operation standard file stored in the container child process directory file comprises:
the cloud service runtime decodes the container operation standard file stored in the container sub-process directory file, and writes the environment variables required by container operation into the decoded container operation standard file;
recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
5. The container creation method of claim 1, wherein the writing of container configuration information into a container operation standard file stored in a container child process directory file comprises:
the cloud service runtime decodes the container operation standard file stored in the container subprocess directory file, and writes a hook function required by container operation into the decoded container operation standard file;
and recoding the written container operation standard file, and flushing the container operation standard file into the container subprocess directory file.
6. The container creation method of claim 1, wherein the writing, by the cloud service runtime, container configuration information into a container operation standard file according to the container creation request comprises:
and the cloud service runtime receives the container creation request, initializes the container, and writes container configuration information into a container operation standard file, wherein the initialization comprises setting a printing path of a system log.
7. The container creation method of any of claims 1 to 6, wherein the advanced container runtime initiates a container creation request to a cloud services runtime comprising:
the advanced container runtime initiates a container creation request to the cloud service runtime in response to the received container runtime request.
8. The container creation method of claim 7, wherein the container creation method further comprises:
the method comprises the steps that a container operation request initiated by a user is received by a runtime command line interface, and the container operation request is analyzed to generate corresponding request parameters;
the runtime command line interface verifies the request parameters;
when the request parameter checks pass, the runtime command line interface sends the container run request to the advanced container runtime.
9. A container creation system, comprising:
the advanced container runtime is used for initiating a container creation request to the cloud service runtime;
when the cloud service is operated, the cloud service is used for writing container configuration information into a container operation standard file stored in a container subprocess directory file according to the container creation request;
and the bottom layer container operation is used for executing container creation according to the container configuration information.
10. The container creation system of claim 9, further comprising a runtime command line interface to receive a user initiated container operation request and parse the container operation request to generate corresponding request parameters;
the runtime command line interface is further configured to verify the request parameter, and when the request parameter is verified, the runtime command line interface sends the container operation request to the advanced container runtime;
the advanced container runtime is used for initiating the container creation request to the cloud service runtime according to the container operation request.
11. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the container creation method of any one of claims 1 to 8 when executing the program.
12. A computer storage medium having computer executable instructions stored thereon, which when executed by a processor, are configured to implement the container creation method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211504064.6A CN115904623A (en) | 2022-11-28 | 2022-11-28 | Container creation method and system, electronic device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211504064.6A CN115904623A (en) | 2022-11-28 | 2022-11-28 | Container creation method and system, electronic device, and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115904623A true CN115904623A (en) | 2023-04-04 |
Family
ID=86472455
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211504064.6A Pending CN115904623A (en) | 2022-11-28 | 2022-11-28 | Container creation method and system, electronic device, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115904623A (en) |
-
2022
- 2022-11-28 CN CN202211504064.6A patent/CN115904623A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2568408B1 (en) | Information processing device, information processing method, and program distribution system | |
| US9614931B2 (en) | Identifying a resource set require for a requested application and launching the resource set in a container for execution in a host operating system | |
| US20100205604A1 (en) | Systems and methods for efficiently running multiple instances of multiple applications | |
| US20130132950A1 (en) | Automation of virtual machine installation by splitting an installation into a minimal installation and customization | |
| KR20060047766A (en) | Systems and methods for development of emulated devices in a virtual machine environment | |
| US9501296B2 (en) | Hypervisor automation manager for starting an operation system with customization data from a disk image | |
| US9164879B2 (en) | Role-oriented testbed environments for use in test automation | |
| WO2014200511A1 (en) | Unified extensible firmware interface (uefi) driver and protocol | |
| US9672047B1 (en) | Systems and methods for accessing a bootable partition on a serial peripheral interface device | |
| US6961848B2 (en) | System and method for supporting legacy operating system booting in a legacy-free system | |
| WO2018090528A1 (en) | Method and system for mirror image package preparation and application operation | |
| CN114020621A (en) | Debugging method, electronic device and storage medium | |
| US8484616B1 (en) | Universal module model | |
| US10185573B2 (en) | Caching based operating system installation | |
| CN115291946A (en) | Hongmong system transplanting method, device, electronic equipment and readable medium | |
| CN113741954A (en) | System software generation method and device, electronic equipment and storage medium | |
| US11106380B2 (en) | Migration of storage for workloads between desktop and cloud environments | |
| CN115904623A (en) | Container creation method and system, electronic device, and storage medium | |
| WO2022199136A1 (en) | Application modification method, and system, cluster, medium and program product | |
| CN114026540B (en) | System and method for supporting and negotiating multiple API versions across multiple products | |
| US20100251236A1 (en) | In-Process Intermediary To Create Virtual Processes | |
| US10394722B1 (en) | Managing alt-mode interfaces of a USB Type-C device | |
| CN115129365B (en) | Method for realizing application program portability based on IPSAN and application | |
| CN115202830B (en) | Root file system preparation method, system, computing device and readable storage medium | |
| KR20110068302A (en) | System and method for controlling access based on shell in unix/linux system |
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 |