CN113656148A - Container management method and device, electronic equipment and readable storage medium - Google Patents
Container management method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN113656148A CN113656148A CN202110961992.4A CN202110961992A CN113656148A CN 113656148 A CN113656148 A CN 113656148A CN 202110961992 A CN202110961992 A CN 202110961992A CN 113656148 A CN113656148 A CN 113656148A
- Authority
- CN
- China
- Prior art keywords
- container
- management
- operation request
- target
- created
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title description 149
- 238000000034 method Methods 0.000 claims abstract description 48
- 230000004044 response Effects 0.000 claims abstract description 14
- 238000013507 mapping Methods 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 14
- 238000004891 communication Methods 0.000 claims description 12
- 238000012217 deletion Methods 0.000 claims description 10
- 230000037430 deletion Effects 0.000 claims description 10
- 230000005764 inhibitory process Effects 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 9
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000012546 transfer Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- KKIMDKMETPPURN-UHFFFAOYSA-N 1-(3-(trifluoromethyl)phenyl)piperazine Chemical compound FC(F)(F)C1=CC=CC(N2CCNCC2)=C1 KKIMDKMETPPURN-UHFFFAOYSA-N 0.000 description 1
- 230000001133 acceleration Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45587—Isolation or security of virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application belongs to the technical field of containers, and discloses a method, a device, electronic equipment and a readable storage medium for managing containers, wherein the method comprises the steps of receiving a container operation request sent by a management container aiming at a target container, wherein the target container is a created or to-be-created service container in the management container; judging whether the container operation request meets a preset operation permission condition, if so, executing the container operation request aiming at the target container; otherwise, a failure response message is returned to the management container. Therefore, the container operation of the management container is filtered, and the unrecoverable safety problem caused by misoperation of a user and electronic equipment is avoided.
Description
Technical Field
The present application relates to the field of container technologies, and in particular, to a method and an apparatus for managing a container, an electronic device, and a readable storage medium.
Background
Docker is an open source application container engine. The developer can pack the application and the dependency package into a portable container through Docker, and distribute the container to any Linux machine to realize virtualization.
In the prior art, a user usually remotely logs in an electronic device by using a secure shell protocol (SSH), and remotely controls a service container in the electronic device to execute a corresponding operation based on a root user (root) authority of the electronic device.
However, since the user has root authority of the electronic device, when the user remotely operates the service container of the electronic device through SSH, important files and database data in the electronic device may be deleted due to a user's misoperation.
Therefore, how to reduce the problem of security of the electronic device caused by misoperation of a user when managing the service container in the electronic device is a technical problem to be solved.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method and an apparatus for managing a container, an electronic device, and a readable storage medium, so as to reduce a security problem of the electronic device caused by a user's misoperation when a service container in the electronic device is managed.
In one aspect, a method for managing containers is provided, and is applied to an electronic device including a management container, and the method includes:
receiving a container operation request sent by a management container aiming at a target container, wherein the target container is a created or to-be-created service container in the management container;
judging whether the container operation request meets a preset operation permission condition, if so, executing the container operation request aiming at the target container;
otherwise, a failure response message is returned to the management container.
In the implementation process, the container operation of the management container is filtered, so that the unrecoverable safety problem caused by misoperation of a user and electronic equipment is avoided.
In one embodiment, receiving a container operation request sent by a management container for a target container includes:
receiving a container operation instruction sent by a user terminal by adopting a remote login protocol through a management container, wherein the container operation instruction is sent aiming at least one target container, and the user terminal is connected with the management container based on an application container engine socket protocol;
and receiving a container operation request sent by the management container based on the container operation instruction through the application container engine socket protocol, wherein the container operation request is sent aiming at least one target container.
In the implementation process, the user terminal remotely logs in the management container to remotely control the management container, so that the user terminal cannot have root authority of the electronic equipment, and the safety of the electronic equipment is further improved.
In one embodiment, before receiving a container operation request sent by a management container for a target container, the method further includes:
when determining that a starting command for the management container is received, starting the management container;
mapping a data volume root directory of the electronic equipment into a management container;
establishing remote login connection with a user terminal through a remote login protocol;
and establishing communication connection with the management container by adopting an application container engine socket protocol.
In the implementation process, the communication connection with the management container is established by applying the socket protocol of the container engine, and the management container can be compatible with the DOCKER command line, so that a user does not need to learn other control languages again, and the complicated operation of managing the service container by the user is further simplified.
In one embodiment, the container operation request is used to perform any one or any combination of the following operations:
creating a container, starting the container, deleting the container, stopping the container, mapping a host directory, updating a database, modifying a configuration file, exporting a log file, editing the file and reading and writing data.
In the implementation process, various management operations can be performed on the service container through the container operation request.
In one embodiment, if the container operation request is used to create a container, determining whether the container operation request meets a preset operation permission condition includes:
determining the number of target containers to be created based on the container operation request;
acquiring the created number of created service containers in the electronic equipment;
judging whether the sum of the number to be created and the created number is lower than a specified total number threshold value or not;
wherein the preset operation authority condition is determined based on a specified total number threshold.
In the implementation process, the container operation of the management container is filtered, so that the unrecoverable safety problem caused by misoperation of a user and electronic equipment is avoided.
In one embodiment, if the container operation request is used to delete at least one of the container, start the container, and stop the container, determining whether the container operation request meets a preset operation permission condition includes:
acquiring a target container set corresponding to the container operation request, wherein the target container set comprises at least one service container, and the target container set is a set of at least one service container from deletion prohibition, start prohibition and stop prohibition;
judging whether the target container set contains a target container;
wherein the preset operation authority condition is determined based on the target container set.
In the implementation process, the container operation of the management container is filtered, so that the unrecoverable safety problem caused by misoperation of a user and electronic equipment is avoided.
In one aspect, an apparatus for managing containers is provided, and is applied to an electronic device including a management container, including:
the receiving unit is used for receiving a container operation request sent by the management container aiming at a target container, wherein the target container is a created or to-be-created service container in the management container;
the judging unit is used for judging whether the container operation request meets a preset operation permission condition or not, and if so, executing the container operation request aiming at the target container; otherwise, a failure response message is returned to the management container.
In one embodiment, the receiving unit is configured to:
receiving a container operation instruction sent by a user terminal by adopting a remote login protocol through a management container, wherein the container operation instruction is sent aiming at least one target container, and the user terminal is connected with the management container based on an application container engine socket protocol;
and receiving a container operation request sent by the management container based on the container operation instruction through the application container engine socket protocol, wherein the container operation request is sent aiming at least one target container.
In one embodiment, the receiving unit is further configured to:
when determining that a starting command for the management container is received, starting the management container;
mapping a data volume root directory of the electronic equipment into a management container;
establishing remote login connection with a user terminal through a remote login protocol;
and establishing communication connection with the management container by adopting an application container engine socket protocol.
In one embodiment, the container operation request is used to perform any one or any combination of the following operations:
creating a container, starting the container, deleting the container, stopping the container, mapping a host directory, updating a database, modifying a configuration file, exporting a log file, editing the file and reading and writing data.
In one embodiment, the determining unit is configured to:
if the container operation request is used for creating the container, determining the number to be created of the target containers to be created based on the container operation request;
acquiring the created number of created service containers in the electronic equipment;
judging whether the sum of the number to be created and the created number is lower than a specified total number threshold value or not;
wherein the preset operation authority condition is determined based on a specified total number threshold.
In one embodiment, the determining unit is configured to:
if the container operation request is used for deleting at least one of the container, starting the container and stopping the container, acquiring a target container set corresponding to the container operation request, wherein the target container set comprises at least one service container, and the target container set is a set of at least one service container from deletion prohibition, starting prohibition and stopping prohibition;
judging whether the target container set contains a target container;
wherein the preset operation authority condition is determined based on the target container set.
In one aspect, an electronic device is provided, comprising a processor and a memory, the memory storing computer readable instructions which, when executed by the processor, perform the steps of the method provided in any of the various alternative implementations of container management as described above.
In one aspect, a readable storage medium is provided, on which a computer program is stored, which computer program, when being executed by a processor, is adapted to carry out the steps of the method as provided in any of the various alternative implementations of container management as described above.
In one aspect, a computer program product is provided, which when run on a computer causes the computer to perform the steps of the method as provided in any of the various alternative implementations of container management as described above.
In a method, an apparatus, an electronic device, and a readable storage medium for managing a container provided in an embodiment of the present application, a container operation request sent by a management container for a target container is received, where the target container is a service container created or to be created in the management container; judging whether the container operation request meets a preset operation permission condition, if so, executing the container operation request aiming at the target container; otherwise, a failure response message is returned to the management container. Therefore, the container operation of the management container is filtered, and the unrecoverable safety problem caused by misoperation of a user and electronic equipment is avoided.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic architecture diagram of a container management system according to an embodiment of the present application;
fig. 2 is a flowchart of an implementation of a method for managing containers according to an embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating an implementation of a method for creating a container according to an embodiment of the present disclosure;
FIG. 4 is a flowchart illustrating an implementation of a method for managing containers according to an embodiment of the present disclosure;
fig. 5 is a block diagram illustrating a structure of an apparatus for container management according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
First, some terms referred to in the embodiments of the present application will be described to facilitate understanding by those skilled in the art.
The terminal equipment: may be a mobile terminal, a fixed terminal, or a portable terminal such as a mobile handset, station, unit, device, multimedia computer, multimedia tablet, internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system device, personal navigation device, personal digital assistant, audio/video player, digital camera/camcorder, positioning device, television receiver, radio broadcast receiver, electronic book device, gaming device, or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that the terminal device can support any type of interface to the user (e.g., wearable device), and the like.
A server: the cloud server can be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, and can also be a cloud server for providing basic cloud computing services such as cloud service, a cloud database, cloud computing, cloud functions, cloud storage, network service, cloud communication, middleware service, domain name service, security service, big data and artificial intelligence platform and the like.
Docker: is an open source application container engine. The developer can pack the application and the dependency package into a portable container through Docker, and distribute the container to any Linux machine to realize virtualization.
Host machine: an electronic device for running a management container and/or a service container.
And (4) service container: the method is a virtual Linux running on a host machine and used for processing services.
Managing the container: the virtual Linux running on the host machine can support common file operation instructions and execute a DOCKER client command line to manage the service container and operate the data volume in the service container.
SSH: protocols for providing secure communications for telnet sessions and other web services. In the embodiment of the application, the service container can be remotely logged in to the management container through SSH, and the service container is managed through the related instruction of the management container.
DOCKER command line: a command line refers to a command line that executes user input using a DOCKER client.
Dockend: is a background service for executing the DOCKER command line in the host.
DOCKER management socket: in this embodiment of the present application, a dock management socket of a host is mapped to a management container, a dock client is installed in the management container, and the host provides a dock service to execute a dock command line input by a user at the dock client.
Data volume: when the service container is started, the file directory of the service container can be operated. File directories and data volumes are in one-to-one correspondence.
Data volume root directory: the data volumes for all the initiated service containers are under this directory. In the embodiment of the present application, the data root directory is mapped into the management container. The data volume catalogs of all the service containers can be seen through the management container, and then the data volumes of all the service containers can be operated.
In order to reduce the security problem of an electronic device caused by misoperation of a user when a service container in the electronic device is managed, embodiments of the present application provide a method, an apparatus, an electronic device, and a readable storage medium for managing a container.
Fig. 1 is a schematic structural diagram of a container management system according to an embodiment of the present disclosure. The service container management system comprises electronic equipment and a user terminal.
The electronic device may be a server or a terminal device, and is not limited herein. The electronic device comprises a management container and one or more service containers. The user terminal may be a terminal device.
A user terminal: and remotely logging in a management container in the electronic equipment through a remote login protocol, and sending a container operation instruction to the management container so as to manage the business container in the electronic equipment through the management container.
Specifically, a user can remotely log in a management container in the electronic device through a user terminal based on a remote login protocol, and send a container operation instruction to the management container through the remote login protocol, so as to remotely control the management container to perform operations such as container creation and deletion in the electronic device.
The remote login protocol is a protocol for remotely logging in other devices. Alternatively, the telnet protocol may be the SSH protocol.
An electronic device: the management container receives a container operation instruction sent by the user terminal, and based on the container operation instruction, a container operation request is sent to the electronic equipment by an application container engine socket protocol process through the application container engine socket protocol process. After receiving the container operation request, the electronic device judges whether the container operation request meets a preset operation authority condition or not through an operation authority judgment process, if so, executes the container operation request aiming at the target container, and otherwise, returns a failure response message to the management container.
Alternatively, the application container engine socket protocol may manage sockets for DOCKER.
Therefore, the management container is arranged in the electronic equipment, the user terminal can remotely log in the management container in the electronic equipment and acquire the root authority of the management container without acquiring the root authority of the electronic equipment, the safety problem of the electronic equipment caused by misoperation of the user on the electronic equipment is avoided, the container operation request of the management container can be filtered by the electronic equipment, and the safety problem of the electronic equipment caused by misoperation of the user is further reduced.
In the embodiment of the present application, an execution subject is an electronic device including a management container, and referring to fig. 2, an implementation flowchart of a method for managing a container provided in the embodiment of the present application is specifically described with reference to the electronic device shown in fig. 1, where the implementation flowchart of the method is as follows:
step 200: and receiving a container operation request sent by the management container aiming at the target container.
Specifically, when step 200 is executed, the following steps may be adopted:
s2001: and receiving a container operation instruction sent by a user terminal by adopting a remote login protocol through the management container.
Specifically, the container operation instruction is sent for at least one target container, that is, one or more target containers may be used, and a user may control the batch containers. The target container is a business container in the electronic device. The user terminal and the management container are connected based on an application container engine socket protocol.
The management container is a virtual Linux in the electronic device, can support remote login protocols such as SSH, and can be preset with commonly used commands, such as File operation commands of a Visual identification system (VI), a File Transfer Protocol (FTP), a simple File Transfer Protocol (TFTP), and the like. The user can control the business container to execute the set file operation and other commands through the management container. The user remotely logs in the management container through a remote login protocol, has root authority of the management container, and can install required software in the management container according to actual application requirements.
In one embodiment, the user terminal sends a container operation instruction for one or more target containers to the management container through the SSH protocol. The management container receives a container operation instruction sent by the user terminal.
Thus, the user can send a container operation instruction to the management container.
S2002: and receiving a container operation request sent by the management container based on the container operation instruction through an application container engine socket protocol.
Specifically, the management container sends a container operation request to the electronic device through a container engine socket protocol based on the container operation instruction.
Wherein the container operation request is sent for at least one target container. The container operation request is used for executing any one or any combination of the following operations:
alternatively, the container operation request may be generated by executing a script file preset in the management container by the user, for example, updating the database, modifying the configuration file, exporting the log file, and the like.
That is, the user terminal may transmit a container operation instruction for executing the specified script file to the management container. The management container can execute the specified script file according to the container operation instruction so as to send a container operation request corresponding to the specified script file to the electronic equipment.
Wherein, the container operation request is used for executing any one or any combination of the following operations:
creating a container, starting the container, deleting the container, stopping the container, mapping a host directory, updating a database, modifying a configuration file, exporting a log file, editing the file and reading and writing data.
In practical application, the container operation request may also be set according to a practical application scenario, which is not limited herein.
In one embodiment, the management container inputs a DOKER command line for sending a container operation request at the DOKER client based on the container operation command. The DOCKER client executes the DOCKER command line to send a container operation request to the electronic device through the DOCKER management socket. The electronic device receives a container operation request sent by the management container through the docked service.
In this way, the management container can send a container operation request to the electronic device.
Further, before performing step 200, the user terminal may log in the management container remotely, specifically including the following steps:
the first step is as follows: the electronic device starts the management container when determining that a start command for the management container is received.
The second step is that: the electronic device maps the data volume root directory into a management container.
Specifically, after receiving the command to start the management container, the electronic device maps the application container engine socket protocol and the data volume root directory in the electronic device to the management container.
The data volume root directory comprises data volume directories in all service containers in the electronic equipment.
The third step: the user terminal establishes remote login connection with the management container through a remote login protocol, so that the user terminal can remotely log in the management container.
Specifically, the user terminal remotely logs in the management container in the electronic device through a remote login protocol.
In one embodiment, a user sends a telnet request containing a login account number and a login password to the management container via a telnet protocol. And after receiving the remote login request, the management container acquires a login account and a login password in the remote login request, verifies the login account and the login password, sends a login success response message to the user terminal if the verification is confirmed to be passed, and otherwise sends a login failure response message to the user terminal.
Furthermore, the user terminal can remotely modify a login password for logging in the management container through a remote login protocol.
The login account and the login password are used for verifying whether the user has the authority to remotely log in the management container.
Therefore, the user can remotely log in and control the management container, and further manage each service container in the electronic equipment through the management container.
The fourth step: the electronic equipment adopts an application container engine socket protocol to establish communication connection with the management container.
Specifically, a dock client is set in the management container, and the user may send various operation requests to the electronic device through the dock command line. And the electronic equipment executes a corresponding container operation request aiming at each service container through the DOCKER service.
It should be noted that, a user may send a container operation request for one or more service containers to the electronic device through the application of the container engine socket protocol, so that batch management of multiple service containers is implemented.
Therefore, after the management container is started, the user terminal can remotely log in the management container to obtain the root authority of the management container, operate the data volume in each service container in the electronic equipment based on the root authority and the data volume root directory of the electronic equipment, and manage the service container in the electronic equipment through the management container by applying a container engine socket protocol.
Step 201: and judging whether the container operation request meets a preset operation authority condition, if so, executing the step 202, otherwise, executing the step 203.
Specifically, the preset operation permission condition may be determined based on any one or any combination of the following parameters:
specifying a number to create threshold, specifying a total number threshold, a target container set, specifying a prohibited mapping directory, and specifying a prohibited instruction.
Wherein, the threshold value of the number to be created is set as the maximum container number when the container is created each time. The total number threshold is specified as a maximum number of receptacles in the set electronic device. The target container set is a set of at least one service container from deletion inhibition, starting inhibition and stopping inhibition. And designating the mapping prohibition directory as a data volume directory which is set to prohibit mapping to the service container. The designated prohibition instruction is an operation instruction set to prohibit execution of the management container.
In actual application, the preset operation permission condition, the specified number threshold to be created, the specified total number threshold, the target container set, the specified prohibited mapping directory and the specified prohibited instruction may all be set according to an actual application scenario, and may also include other conditions, which are not limited herein.
Step 202: the container operation request is executed for the target container.
Step 203: a failure response message is returned to the management container.
The above embodiments are illustrated below using several specific application scenarios.
Scene 1: a business container is created. Referring to fig. 3, a flow chart of an implementation of a method of creating a container is shown. The specific implementation flow of the method is as follows:
step 301: and receiving a container operation request sent by the management container and used for creating the target container.
Step 302: and determining the number to be created of the target containers to be created based on the container operation request.
Specifically, the number to be created of the target container included in the container operation request is acquired.
For example, the number to be created is 3, i.e., the management container requests the creation of 3 service containers in the electronic device.
Step 303: and acquiring the created quantity of the created service containers in the electronic equipment.
For example, the created number is 5, i.e. 5 service containers have been created in the electronic device.
Step 304: and judging whether the sum of the number to be created and the created number is lower than a specified total number threshold value, if so, executing the step 305, and otherwise, executing the step 306.
Specifically, the sum of the to-be-created number and the created number is determined, and it is determined whether the sum is lower than a specified total number threshold.
This is because the number of service containers that can be set in the electronic device is limited, and if the number of service containers exceeds the limit, the container creation operation is not allowed to be performed.
Further, it may be determined whether the number to be created is lower than a specified threshold value of the number to be created, if so, step 305 is performed, otherwise, step 306 is performed.
In this way, the maximum number of service containers created at a time can be limited.
Further, it may be determined whether the sum is lower than a specified total number threshold and the number to be created is lower than a specified number to be created threshold, if yes, step 305 is performed, otherwise, step 306 is performed.
Further, according to the container operation request, a data volume directory mapped to the container to be created may be determined, and it is determined whether the data volume directory includes information of a mapping prohibition directory, if so, step 305 is performed, otherwise, step 306 is performed.
The data volume directory is a file directory which can operate the service container when the service container is started. The file directories and the data volume directories are in one-to-one correspondence.
The mapping prohibition directory information is set as the directory information of the preset mapping prohibition electronic equipment.
Therefore, the risk that the business container operates important sensitive files in the electronic equipment can be avoided, and the safety of the host machine is improved.
In this way, the number of service containers created at a time can be limited, and the total number of service containers allowed to be created in the electronic device can be limited.
Step 305: a target container is created.
Step 306: a failure response message is returned to the management container.
Scene 2: and managing the service container. Referring to fig. 4, a flow chart of an embodiment of a method for managing containers is shown. The specific implementation flow of the method is as follows:
step 400: and receiving a container operation request sent by the management container and used for managing the target container.
In one embodiment, a container operation request sent by a management container to delete a target container is received.
In one embodiment, a container operation request sent by a management container to start a target container is received.
In one embodiment, a container operation request sent by a management container to stop a target container is received.
In this way, the operation of the service container can be managed.
Step 401: and acquiring a target container set corresponding to the container operation request.
Specifically, the target container set includes at least one service container, and the target container set is a set of at least one service container from deletion prohibition, start prohibition, and stop prohibition.
When step 401 is executed, the following modes may be adopted:
mode 1: and if the container operation request is used for deleting the target container, acquiring a target container set containing the service container forbidden to be deleted.
This is because in some application scenarios, some service containers in the electronic device are not allowed to be deleted.
Mode 2: and if the container operation request is used for starting the target container, acquiring a target container set containing the service container which is prohibited from being started.
This is because in some application scenarios, some service containers in the electronic device are not allowed to be started for a certain period of time.
Mode 3: and if the container operation request is used for stopping the target container, acquiring a target container set containing the service container prohibited from stopping.
This is because in some application scenarios, some service containers in the electronic device are not allowed to stop.
In this way, preset target container sets of various types can be obtained.
Step 402: and judging whether the target container set does not contain the target container, if so, executing the step 403, otherwise, executing the step 404.
Wherein the preset operation authority condition is determined based on the target container set.
Further, the number of target containers of the container operation request may be determined, and it is determined whether the number is lower than a preset operation number threshold, if so, step 403 is performed, otherwise, step 404 is performed.
In practical applications, the preset operation number threshold may be set according to practical application scenarios, for example, 5, which is not limited herein.
In this way, the number of target containers for managing container batch operations may be limited.
Step 403: and executing the container operation request aiming at the target container.
Step 404: a failure response message is returned to the management container.
In this way, deletion, start, and stop of a particular container can be prohibited, thereby avoiding business risk problems due to container deletion, start, and stop operations.
Further, when determining whether the container operation request meets the preset operation permission condition, the following modes may also be adopted:
mode 1: and judging whether the container operation request for data writing has read-write permission or not.
Mode 2: and judging whether the container operation request for exporting the log file has log export authority or not.
Mode 3: and judging whether the container operation request for modifying the configuration file has a configuration modification permission.
Mode 4: and judging whether the container operation request for updating the database has the database modification authority or not.
Mode 5: and judging whether the container operation request for mapping the host directory has the mapping authority or not.
Mode 6: and judging whether the container operation request is a specified request.
In practical application, the preset operation permission condition may be set according to a practical application scenario, which is not limited herein.
In the embodiment of the application, the management container is installed in the electronic device, namely the host, the user terminal remotely logs in the management container in the host, only the root authority of the management container can be obtained, but the root authority of the host cannot be obtained, the remote login protocol is isolated from the host, the user is endowed with the capability of managing the service container in the host on the premise of ensuring the safety of the host, the risk of unrecoverable host caused by misoperation of the user is avoided, the safety of the host is protected, moreover, after the user remotely logs in the management container, the batch service containers can be operated through the management container, the tedious operation that the user can only operate a single service container is simplified, the efficiency of service container management is improved, further, the host filters the container operation request sent by the management container aiming at the service container, and the operation authority of the management container is limited, the method ensures that the access authority of the user to the service container is controllable, further improves the safety of the host, and finally, the management container can be compatible with the DOCKER command line, so that the user does not need to learn other control languages again, and the complicated operation of managing the service container by the user is further simplified.
Based on the same inventive concept, the embodiment of the present application further provides a device for container management, and as the principles of the device and the apparatus for solving the problems are similar to those of a method for container management, the implementation of the device can refer to the implementation of the method, and repeated details are not repeated.
As shown in fig. 5, which is a schematic structural diagram of an apparatus for managing containers according to an embodiment of the present application, applied to an electronic device including a management container, the apparatus includes:
a receiving unit 501, configured to receive a container operation request sent by a management container for a target container, where the target container is a service container created or to be created in the management container;
a determining unit 502, configured to determine whether the container operation request meets a preset operation permission condition, and if so, execute the container operation request for the target container; otherwise, a failure response message is returned to the management container.
In one embodiment, the receiving unit 501 is configured to:
receiving a container operation instruction sent by a user terminal by adopting a remote login protocol through a management container, wherein the container operation instruction is sent aiming at least one target container, and the user terminal is connected with the management container based on an application container engine socket protocol;
and receiving a container operation request sent by the management container based on the container operation instruction through the application container engine socket protocol, wherein the container operation request is sent aiming at least one target container.
In one embodiment, the receiving unit 501 is further configured to:
when determining that a starting command for the management container is received, starting the management container;
mapping a data volume root directory of the electronic equipment into a management container;
establishing remote login connection with a user terminal through a remote login protocol;
and establishing communication connection with the management container by adopting an application container engine socket protocol.
In one embodiment, the container operation request is used to perform any one or any combination of the following operations:
creating a container, starting the container, deleting the container, stopping the container, mapping a host directory, updating a database, modifying a configuration file, exporting a log file, editing the file and reading and writing data.
In one embodiment, the determining unit 502 is configured to:
if the container operation request is used for creating the container, determining the number to be created of the target containers to be created based on the container operation request;
acquiring the created number of created service containers in the electronic equipment;
judging whether the sum of the number to be created and the created number is lower than a specified total number threshold value or not;
wherein the preset operation authority condition is determined based on a specified total number threshold.
In one embodiment, the determining unit 502 is configured to:
if the container operation request is used for deleting at least one of the container, starting the container and stopping the container, acquiring a target container set corresponding to the container operation request, wherein the target container set comprises at least one service container, and the target container set is a set of at least one service container from deletion prohibition, starting prohibition and stopping prohibition;
judging whether the target container set contains a target container;
wherein the preset operation authority condition is determined based on the target container set.
In a method, an apparatus, an electronic device, and a readable storage medium for managing a container provided in an embodiment of the present application, a container operation request sent by a management container for a target container is received, where the target container is a service container created or to be created in the management container; judging whether the container operation request meets a preset operation permission condition, if so, executing the container operation request aiming at the target container; otherwise, a failure response message is returned to the management container. Therefore, the container operation of the management container is filtered, and the unrecoverable safety problem caused by misoperation of a user and electronic equipment is avoided.
Fig. 6 shows a schematic structural diagram of an electronic device 6000. Referring to fig. 6, the electronic device 6000 includes: processor 6010 and memory 6020 may optionally further include a power supply 6030, a display unit 6040, and an input unit 6050.
The processor 6010 is a control center of the electronic apparatus 6000, connects various components using various interfaces and lines, and performs various functions of the electronic apparatus 6000 by running or executing software programs and/or data stored in the memory 6020, thereby integrally monitoring the electronic apparatus 6000.
In the embodiment of the present application, the processor 6010, when calling the computer program stored in the memory 6020, executes the method of service container management provided in the embodiment shown in fig. 2.
Alternatively, processor 6010 may include one or more processing units; preferably, processor 6010 may integrate an application processor that handles mainly the operating system, user interfaces, applications, etc. and a modem processor that handles mainly wireless communications. It is to be appreciated that the modem processor described above may not be integrated into processor 6010. In some embodiments, the processor, memory, and/or memory may be implemented on a single chip, or in some embodiments, they may be implemented separately on separate chips.
The memory 6020 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, various applications, and the like; the storage data area may store data created according to the use of the electronic device 6000, and the like. In addition, the memory 6020 may include high-speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The electronic device 6000 further includes a power supply 6030 (e.g., a battery) for powering the various components, which may be logically connected to the processor 6010 via a power management system to manage charging, discharging, and power consumption via the power management system.
The display unit 6040 may be configured to display information input by a user or information provided to the user, various menus of the electronic device 6000, and the like, and in the embodiment of the present invention, the display unit is mainly configured to display a display interface of each application in the electronic device 6000 and objects such as texts and pictures displayed in the display interface. The display unit 6040 may include a display panel 6041. The Display panel 6041 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The input unit 6050 may be used to receive information such as numbers or characters input by a user. The input unit 6050 may include a touch panel 6051 and other input devices 6052. Touch panel 6051, also referred to as a touch screen, may collect touch operations by a user on or near touch panel 6051 (e.g., operations by a user on or near touch panel 6051 using a finger, a stylus, or any other suitable object or attachment).
Specifically, the touch panel 6051 may detect a touch operation by the user, detect signals resulting from the touch operation, convert the signals into touch point coordinates, send the touch point coordinates to the processor 6010, receive a command sent from the processor 6010, and execute the command. In addition, the touch panel 6051 can be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. Other input devices 6052 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, power on and off keys, etc.), a trackball, a mouse, a joystick, and the like.
Of course, the touch panel 6051 may cover the display panel 6041, and when the touch panel 6051 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 6010 to determine the type of the touch event, and then the processor 6010 provides a corresponding visual output on the display panel 6041 according to the type of the touch event. Although in fig. 6, the touch panel 6051 and the display panel 6041 are two separate components to implement the input and output functions of the electronic device 6000, in some embodiments, the touch panel 6051 and the display panel 6041 may be integrated to implement the input and output functions of the electronic device 6000.
The electronic device 6000 may also include one or more sensors, such as pressure sensors, gravitational acceleration sensors, proximity light sensors, and the like. Of course, the electronic device 6000 may also include other components such as a camera, which are not shown in fig. 6 and will not be described in detail since they are not the components used in this embodiment of the present application.
Those skilled in the art will appreciate that fig. 6 is merely an example of an electronic device and is not limiting of electronic devices and may include more or fewer components than those shown, or some components may be combined, or different components.
In an embodiment of the present application, a readable storage medium has a computer program stored thereon, and when the computer program is executed by a processor, the communication device may perform the steps in the above embodiments.
For convenience of description, the above parts are separately described as modules (or units) according to functional division. Of course, the functionality of the various modules (or units) may be implemented in the same one or more pieces of software or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application 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 application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. 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.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (14)
1. A method for managing containers, applied to an electronic device including a management container, the method comprising:
receiving a container operation request sent by the management container aiming at a target container, wherein the target container is a created or to-be-created business container in the management container;
judging whether the container operation request meets a preset operation permission condition, if so, executing the container operation request aiming at the target container;
otherwise, returning a failure response message to the management container.
2. The method of claim 1, wherein the receiving the container operation request sent by the management container for the target container comprises:
receiving a container operation instruction sent by a user terminal by adopting a remote login protocol through the management container, wherein the container operation instruction is sent aiming at least one target container, and the user terminal is connected with the management container based on an application container engine socket protocol;
receiving, by an application container engine socket protocol, a container operation request sent by the management container based on the container operation instruction, where the container operation request is sent for the at least one target container.
3. The method of claim 2, wherein prior to said receiving a container operation request sent by the management container for a target container, further comprising:
when determining that a starting command for the management container is received, starting the management container;
mapping the data volume root directory of the electronic equipment to the management container;
establishing remote login connection with the user terminal through a remote login protocol;
and establishing communication connection with the management container by adopting the application container engine socket protocol.
4. A method according to any one of claims 1 to 3, wherein the container operation request is for performing any one or any combination of the following operations:
creating a container, starting the container, deleting the container, stopping the container, mapping a host directory, updating a database, modifying a configuration file, exporting a log file, editing the file and reading and writing data.
5. The method of claim 4, wherein if the container operation request is for creating a container, the determining whether the container operation request meets a preset operation permission condition comprises:
determining the number of target containers to be created based on the container operation request;
acquiring the created number of the created service containers in the electronic equipment;
judging whether the sum of the number to be created and the created number is lower than a specified total number threshold value or not;
wherein the preset operation permission condition is determined based on the specified total number threshold.
6. The method of claim 4, wherein if the container operation request is used for at least one of deleting a container, starting a container, and stopping a container, the determining whether the container operation request meets a preset operation permission condition includes:
acquiring a target container set corresponding to the container operation request, wherein the target container set comprises at least one service container, and the target container set is a set of at least one service container from deletion prohibition, start prohibition and stop prohibition;
judging whether the target container set contains the target container;
wherein the preset operation permission condition is determined based on the target container set.
7. An apparatus for managing containers, applied to an electronic device including a management container, comprising:
a receiving unit, configured to receive a container operation request sent by the management container for a target container, where the target container is a service container created or to be created in the management container;
the judging unit is used for judging whether the container operation request meets a preset operation permission condition or not, and if so, executing the container operation request aiming at the target container; otherwise, returning a failure response message to the management container.
8. The apparatus of claim 7, wherein the receiving unit is to:
receiving a container operation instruction sent by a user terminal by adopting a remote login protocol through the management container, wherein the container operation instruction is sent aiming at least one target container, and the user terminal is connected with the management container based on an application container engine socket protocol;
receiving, by an application container engine socket protocol, a container operation request sent by the management container based on the container operation instruction, where the container operation request is sent for the at least one target container.
9. The apparatus of claim 8, wherein the receiving unit is further configured to:
when determining that a starting command for the management container is received, starting the management container;
mapping the data volume root directory of the electronic equipment to the management container;
establishing remote login connection with the user terminal through a remote login protocol;
and establishing communication connection with the management container by adopting the application container engine socket protocol.
10. The apparatus according to any one of claims 7 to 9, wherein the container operation request is for performing any one or any combination of the following operations:
creating a container, starting the container, deleting the container, stopping the container, mapping a host directory, updating a database, modifying a configuration file, exporting a log file, editing the file and reading and writing data.
11. The apparatus of claim 10, wherein the determining unit is to:
if the container operation request is used for creating a container, determining the number to be created of the target containers to be created based on the container operation request;
acquiring the created number of the created service containers in the electronic equipment;
judging whether the sum of the number to be created and the created number is lower than a specified total number threshold value or not;
wherein the preset operation permission condition is determined based on the specified total number threshold.
12. The apparatus of claim 11, wherein the determining unit is to:
if the container operation request is used for deleting at least one of a container, starting the container and stopping the container, acquiring a target container set corresponding to the container operation request, wherein the target container set comprises at least one service container, and the target container set is a set of at least one service container from deletion inhibition, starting inhibition and stopping inhibition;
judging whether the target container set contains the target container;
wherein the preset operation permission condition is determined based on the target container set.
13. An electronic device comprising a processor and a memory, the memory storing computer readable instructions that, when executed by the processor, perform the method of any of claims 1-6.
14. A readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110961992.4A CN113656148B (en) | 2021-08-20 | 2021-08-20 | Container management method, device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110961992.4A CN113656148B (en) | 2021-08-20 | 2021-08-20 | Container management method, device, electronic equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113656148A true CN113656148A (en) | 2021-11-16 |
| CN113656148B CN113656148B (en) | 2024-02-06 |
Family
ID=78480566
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110961992.4A Active CN113656148B (en) | 2021-08-20 | 2021-08-20 | Container management method, device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113656148B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114115066A (en) * | 2021-12-03 | 2022-03-01 | 中国建设银行股份有限公司 | Bare device control method and target electronic device |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101378368A (en) * | 2008-09-28 | 2009-03-04 | 腾讯科技（深圳）有限公司 | Method and system for information interaction |
| CN103780428A (en) * | 2014-01-17 | 2014-05-07 | 广州亦云信息技术有限公司 | Centralized resource management method and system applied to cloud architecture |
| CN107634951A (en) * | 2017-09-22 | 2018-01-26 | 携程旅游网络技术（上海）有限公司 | Docker vessel safeties management method, system, equipment and storage medium |
| CN107643940A (en) * | 2017-09-26 | 2018-01-30 | 华为技术有限公司 | Container creation method, relevant device and computer-readable storage medium |
| CN108306908A (en) * | 2016-12-24 | 2018-07-20 | 深圳壹账通智能科技有限公司 | Management optimization method and device based on Docker |
| CN111200595A (en) * | 2019-12-20 | 2020-05-26 | 北京淇瑀信息科技有限公司 | Authority management method and device for accessing container and electronic equipment |
| CN111510444A (en) * | 2020-04-09 | 2020-08-07 | 上海云励科技有限公司 | Remote access method, system, server and access auxiliary component of container |
| CN111885203A (en) * | 2020-08-04 | 2020-11-03 | 浪潮云信息技术股份公司 | Method for remote management based on CMSP |
| CN113076170A (en) * | 2021-06-03 | 2021-07-06 | 统信软件技术有限公司 | Remote assistance method, system, device, computing equipment and storage medium |
| CN113169952A (en) * | 2018-09-29 | 2021-07-23 | 北京连云决科技有限公司 | Container cloud management system based on block chain technology |
-
2021
- 2021-08-20 CN CN202110961992.4A patent/CN113656148B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101378368A (en) * | 2008-09-28 | 2009-03-04 | 腾讯科技（深圳）有限公司 | Method and system for information interaction |
| CN103780428A (en) * | 2014-01-17 | 2014-05-07 | 广州亦云信息技术有限公司 | Centralized resource management method and system applied to cloud architecture |
| CN108306908A (en) * | 2016-12-24 | 2018-07-20 | 深圳壹账通智能科技有限公司 | Management optimization method and device based on Docker |
| CN107634951A (en) * | 2017-09-22 | 2018-01-26 | 携程旅游网络技术（上海）有限公司 | Docker vessel safeties management method, system, equipment and storage medium |
| CN107643940A (en) * | 2017-09-26 | 2018-01-30 | 华为技术有限公司 | Container creation method, relevant device and computer-readable storage medium |
| CN113169952A (en) * | 2018-09-29 | 2021-07-23 | 北京连云决科技有限公司 | Container cloud management system based on block chain technology |
| CN111200595A (en) * | 2019-12-20 | 2020-05-26 | 北京淇瑀信息科技有限公司 | Authority management method and device for accessing container and electronic equipment |
| CN111510444A (en) * | 2020-04-09 | 2020-08-07 | 上海云励科技有限公司 | Remote access method, system, server and access auxiliary component of container |
| CN111885203A (en) * | 2020-08-04 | 2020-11-03 | 浪潮云信息技术股份公司 | Method for remote management based on CMSP |
| CN113076170A (en) * | 2021-06-03 | 2021-07-06 | 统信软件技术有限公司 | Remote assistance method, system, device, computing equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114115066A (en) * | 2021-12-03 | 2022-03-01 | 中国建设银行股份有限公司 | Bare device control method and target electronic device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113656148B (en) | 2024-02-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3657358B1 (en) | Method, device and system for persistent data processing, and readable storage medium | |
| CN109922106B (en) | Cloud mobile phone system realized based on Docker container | |
| US9384098B1 (en) | Portable data archiving device | |
| CN110457894B (en) | root authority distribution method and device, storage medium and terminal equipment | |
| US10922445B2 (en) | Computing systems and methods | |
| CN109657448B (en) | Method and device for acquiring Root authority, electronic equipment and storage medium | |
| CN110286768B (en) | Virtual object display method, terminal device and computer-readable storage medium | |
| US20190199795A1 (en) | Method and device for synchronizing backup data, storage medium, electronic device, and server | |
| CN108090345B (en) | Linux system external command execution method and device | |
| CN109271211A (en) | Method, apparatus of attending to anything else, equipment and the medium of application program | |
| EP3021250B1 (en) | Electronic device and method for suggesting response manual in occurrence of denial | |
| EP3374858A1 (en) | Creating and modifying applications from a mobile device | |
| CN113656148B (en) | Container management method, device, electronic equipment and readable storage medium | |
| CN110865981A (en) | File access method for mobile terminal and mobile terminal thereof | |
| CN108762983B (en) | Multimedia data recovery method and device | |
| CN106648962B (en) | A kind of management method, device and intelligent terminal for opening application more | |
| US9887979B1 (en) | Systems and methods for enabling users to launch applications without entering authentication credentials | |
| CN110263006A (en) | A kind of method and apparatus for downloading file on a user device | |
| CN113742716B (en) | Code running method, device, electronic equipment, storage medium and program product | |
| CN115391277A (en) | Method, device, equipment and medium for detecting directory capacity quota | |
| CN108763357A (en) | Document handling method and relevant apparatus | |
| CN107506231A (en) | A kind of method and system of VDI data protections | |
| CN114050931A (en) | Data transmission method and device, electronic equipment and readable storage medium | |
| CN103052060A (en) | Method for improving information security of mobile terminal and mobile terminal | |
| CN109543420B (en) | Permission configuration method and device based on sud, electronic equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |