CN107766707B - Method and apparatus for responding to user request in application container engine - Google Patents

Method and apparatus for responding to user request in application container engine Download PDF

Info

Publication number
CN107766707B
CN107766707B CN201710958639.4A CN201710958639A CN107766707B CN 107766707 B CN107766707 B CN 107766707B CN 201710958639 A CN201710958639 A CN 201710958639A CN 107766707 B CN107766707 B CN 107766707B
Authority
CN
China
Prior art keywords
user
container
information
image file
management request
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.)
Active
Application number
CN201710958639.4A
Other languages
Chinese (zh)
Other versions
CN107766707A (en
Inventor
代振宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Wave Intelligent Technology Co Ltd
Original Assignee
Suzhou Wave Intelligent Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Suzhou Wave Intelligent Technology Co Ltd filed Critical Suzhou Wave Intelligent Technology Co Ltd
Priority to CN201710958639.4A priority Critical patent/CN107766707B/en
Publication of CN107766707A publication Critical patent/CN107766707A/en
Application granted granted Critical
Publication of CN107766707B publication Critical patent/CN107766707B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31User authentication
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44521Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141Access rights, e.g. capability lists, access control lists, access tables, access matrices

Abstract

The invention discloses a method and a device for responding to a user request in an application container engine. The method comprises the following steps: after a Docker management request of a user is received, acquiring the user type of the user; judging whether the user type of the user is a common user or not; if the user type of the user is a common user, granting the user the authority of managing Docker according to a preset management strategy; and after the user acquires the authority of managing the Docker, responding to the management request of the Docker of the user.

Description

Method and apparatus for responding to user request in application container engine
Technical Field
The present invention relates to the field of information processing, and in particular, to a method and apparatus for responding to a user request in an application container engine.
Background
The Docker is an open-source Application container engine, which allows developers to package their applications and dependencies into a portable container and then distribute them to any popular Linux machine, or to manage and create the Docker container using a client-server (C/S) architecture model using a remote API (Application Programming Interface).
The Docker container is created by Docker mirroring, where the container to mirror relationship is similar to objects and classes in object-oriented programming. With the prevalence of the Docker technology, there are several key points to be solved in the process of managing containers:
1. docker commands that a common user has no execution authority;
2. if the Docker is added into the root group, the user has the authority to execute the Docker, the management authority of the Docker is increased, and the security risk is possibly caused;
3. under the assumption of safe precursor, the common user needs to go through a tedious search process every time the common user executes the search process, and the common user cannot effectively manage the own container. A series of bad results such as time consumption, wrong use, or wrong deletion are easy to occur.
Disclosure of Invention
In order to solve at least one technical problem, the present invention provides a method and apparatus for responding to a user request in an application container engine.
In order to achieve the object of the present invention, the present invention provides a method for responding to a user request in an application container engine, comprising:
after a Docker management request of a user is received, acquiring the user type of the user;
judging whether the user type of the user is a common user or not;
if the user type of the user is a common user, granting the user the authority of managing Docker according to a preset management strategy;
and after the user acquires the authority of managing the Docker, responding to the management request of the Docker of the user.
Wherein, the method also has the following characteristics: the responding to the management request of the user Docker comprises the following steps:
after receiving a management request of a user for establishing a container, outputting list information of a mirror image file;
receiving a target image file selected from the list information by the user;
and establishing a container of the target image file to respond to the management request for establishing the container, and recording the identification information of the container.
Wherein, the method also has the following characteristics: the method further comprises the following steps:
after the container is established, recording the corresponding relation between the identifier of the container and at least one of the following information, wherein the information comprises user information, a container storage address, time information and a mirror image name.
Wherein, the method also has the following characteristics: the responding to the management request of the user Docker comprises the following steps:
after receiving a management request of a user for inquiring a container, acquiring user information in the management request;
searching a container identifier corresponding to user information according to a corresponding relation between the pre-stored user information and the container identifier;
and outputting the information of the container corresponding to the container identification.
Wherein, the method also has the following characteristics: the responding to the management request of the user Docker comprises the following steps:
when a management request of a user for changing the mirror image file of an existing container is received, acquiring user information, identification information of the container and identification information of the changed mirror image file in the management request;
searching identification information of the image file corresponding to the user information according to a corresponding relation between the pre-stored user information and the image file;
judging whether the identification information of the changed image file is in the identification information of the image file corresponding to the user information to obtain a judgment result;
and if the judgment result is that the image file is not in the storage device, deleting the image file in the storage device corresponding to the storage device identification, and loading the image corresponding to the identification information of the changed image file.
An apparatus for responding to a user request in an application container engine, comprising:
the system comprises an acquisition module, a storage module and a processing module, wherein the acquisition module acquires a user type of a user after receiving a Docker management request of the user;
the judging module is used for judging whether the user type of the user is a common user or not;
the authorization module is used for granting the user the authority to manage the Docker according to a preset management strategy if the user type of the user is a common user;
and the response module is used for responding the management request of the Docker of the user after the user acquires the authority of managing the Docker.
Wherein, the device still has following characteristics: the response module includes:
the first output unit is used for outputting the list information of the mirror image file after receiving a management request of a user for establishing a container;
a receiving unit, configured to receive a target image file selected by the user from the list information;
and the establishing unit is used for establishing a container of the target image file so as to respond to the management request for establishing the container, and recording the identification information of the container.
Wherein, the device still has following characteristics: the device further comprises:
and the recording module is used for recording the corresponding relation between the identifier of the container and at least one of the following information after the container is established, wherein the information comprises user information, a container storage address, time information and a mirror image name.
Wherein, the device still has following characteristics: the response module includes:
the first acquisition unit is used for acquiring user information in a management request after receiving the management request of a user query container;
the first searching unit is used for searching the container identifier corresponding to the user information according to the corresponding relation between the pre-stored user information and the container identifier;
and the second output unit is used for outputting the information of the container corresponding to the container identifier.
Wherein, the device still has following characteristics: the response module includes:
the second acquisition module is used for acquiring user information, identification information of the container and identification information of the changed mirror image file in the management request after receiving the management request of changing the mirror image file of the existing container by the user;
the second searching unit is used for searching the identification information of the mirror image file corresponding to the user information according to the corresponding relation between the pre-stored user information and the mirror image file;
the judging unit is used for judging whether the identification information of the changed image file is in the identification information of the image file corresponding to the user information to obtain a judgment result;
and the loading unit is used for deleting the mirror image file in the container corresponding to the container identifier and loading the mirror image corresponding to the identifier information of the changed mirror image file if the judgment result is that the mirror image file is not in the container.
According to the embodiment provided by the invention, the user type is identified and judged, the authorization is carried out on the common user, the guarantee is provided for responding the management request of the Docker of the user, the authority problem is solved, and the application range of the Docker is improved.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.
FIG. 1 is a flow chart of a method for responding to a user request in an application container engine according to the present invention;
fig. 2 is a block diagram of an apparatus for responding to a user request in an application container engine according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
The steps illustrated in the flow charts of the figures may be performed in a computer system such as a set of computer-executable instructions. Also, while a logical order is shown in the flow diagrams, in some cases, the steps shown or described may be performed in an order different than here.
Fig. 1 is a flowchart of a method for responding to a user request in an application container engine according to the present invention. The method shown in fig. 1 comprises:
step 101, after receiving a Docker management request of a user, acquiring a user type of the user;
specifically, a user who initiates a Docker management request needs to acquire the user type of the user before responding to the management request because the existing system has no management authority for a common user;
step 102, judging whether the user type of the user is a common user;
specifically, whether special processing needs to be performed on the user is determined by judging whether the user type of the user is a common user;
103, if the user type of the user is a common user, granting the user the authority to manage the Docker according to a preset management strategy;
specifically, as a common user, the user does not have a management right at present, so that the right needs to be opened for the user, and meanwhile, the security factor is also considered, and a part of the common users can be opened, so that a security policy can be set according to actual needs, and a part of the common users can be controlled to have the right;
and step 104, responding to the management request of the Docker of the user after the user acquires the authority of managing the Docker.
Specifically, after detecting that the user has the right, the management request of the user is responded.
The method provided by the embodiment of the invention authorizes the common user by identifying and judging the user type, provides guarantee for responding the management request of the Docker of the user, solves the authority problem and improves the application range of the Docker.
The method embodiment provided by the present invention is further illustrated below:
in order to realize the response to the user management request, a DockerEngine file is set, wherein the DockerEngine file is a core file and comprises the following functional units:
dockerrrun for creating a container method design;
dockerenter, for entering a container method design;
dockerestory, for destroying a container process design;
dockerrmanage, for integrated management method design.
Wherein, the Docker Engine file needs root authorization, and the specific method for executing the Docker Engine file by a common user comprises the following steps:
[root@node2~]#vim/etc/sudoers
adding
ALL ALL=(root)\
NOPASSWD:/usr/local/Docker-inspur/bin/DockerEngine
When a user needs to establish a container, the processing method is as follows:
after receiving a management request of a user for establishing a container, outputting list information of a mirror image file;
receiving a target image file selected from the list information by the user;
and establishing a container of the target image file to respond to the management request for establishing the container, and recording the identification information of the container.
The method for establishing the container provided by the invention specifically comprises the following steps:
the Dockerrrun method needs to acquire a Docker mirror image list through Docker images and number the list, a user can input the number of which mirror image is used to create a container to create the container, the container runs in the background through-d parameters, and information such as the time of each created container, the created user, the iD number and the like is recorded. Information of a drive and the like to be mounted is fixed under a directory. The vector was mounted by-v.
After the container is established, recording the corresponding relation between the identifier of the container and at least one of the following information, wherein the information comprises user information, a container storage address, time information and a mirror image name.
Specifically, the ID number of the container start is recorded through — cidfile, the date obtains a timestamp, the Docker images obtain the name of the mirror image, then the file name format is $ { USER }, the date, and the content is the container ID number and the name of the mirror image. For example:
file name: root,2017-08-24-09:37:04
Id number: 82c68d872cb0ca591473827c4e8694207a2683919
Mirror image name: 10.166.15.103 5000/Dockermxnet latest
After the easy establishment is completed, a user query request for the established container can be responded, and the method comprises the following steps:
after receiving a management request of a user for inquiring a container, acquiring user information in the management request;
searching a container identifier corresponding to user information according to a corresponding relation between the pre-stored user information and the container identifier;
and outputting the information of the container corresponding to the container identification.
Specifically, the Dockerenter method needs to filter out a current user container information list by using a current user as a keyword through a container information list stored in Dockerrun, list containers of all users and number if the current user is a root user, input a number by the user, list containers of all users and number if the user enters a container root user corresponding to the number, input the number by the user, and delete the containers corresponding to the number.
In the program execution, the Dockerenter traverses all files, prints and numbers information, and stores user names and IDs in an array in a comma separation mode and numbers the user names and IDs. And when the user inputs the corresponding number, a Docker exec-it $ ID/bin/bash command is triggered to enter the container.
Of course, the user may also call Dockerestory to destroy the container, traverse all files, print and number the information, and store the user name, ID, and comma separation into the array and number. And if the user inputs the corresponding serial number, triggering a Docker rm-f $ ID command to destroy the container.
When a management request of a user for changing the mirror image file of an existing container is received, acquiring user information, identification information of the container and identification information of the changed mirror image file in the management request;
searching identification information of the image file corresponding to the user information according to a corresponding relation between the pre-stored user information and the image file;
judging whether the identification information of the changed image file is in the identification information of the image file corresponding to the user information to obtain a judgment result;
and if the judgment result is that the image file is not in the storage device, deleting the image file in the storage device corresponding to the storage device identification, and loading the image corresponding to the identification information of the changed image file.
Specifically, the operations are realized by adopting Dockerrmanage comprehensive management, and the Dockerrmanage method integrates a plurality of methods, including the three methods, and also integrates a commit mirror method, a push mirror method for uploading a mirror image to a private warehouse, and a push mirror method for downloading a mirror image to a local warehouse. For example, entering a destroy container calls the Dockerenter and Dockerestory methods, and when a commit container is used, all files are traversed, information is printed and numbered, and a user name, an ID and commas are separately stored in an array and numbered. The user enters the corresponding number and executes the commit $ ID image name to submit the image. When Push images, Docker images are executed to list and number image lists, image names are numbered, the images are numbered, when a user inputs a corresponding number, the existing image names and tags in the current warehouse are listed, the user is waited to input the image names and tags to be submitted, the image names and tags are not repeated as much as possible, and otherwise the image names and tags are covered. Defaulting the current mirror name tag as the current timestamp, and then executing Docker push IP/image. Pull is similar to push, and performs the reverse operation.
The method of Dockerrun, dockeren, dockeestory and Dockermanager needs to transmit a user name of a common user so as to distinguish which user executes a Docker management command, so that the method is convenient for later recording, screening, entering, deleting and the like to manage the container, and does not interfere with other people and is not interfered by other people.
Because the Docker can only be executed in a root mode, if a general user has a root authority for executing the Docker in a mode of adding a group, the general user can randomly execute a Docker command, which results in insecurity of the container and easily causes misoperation, therefore, when the user requests to execute a request for establishing, querying, deleting and changing the container, the user needs to be further authenticated, whether the authority for executing the specific operation exists is judged, and the operation is responded after the authority is judged to exist. In the present invention example, four methods of Dockerrun, dockerer, dockeestory, Dockermanager are written into dockerenine and are authorized by root to dockerenine to provide access security.
In order to transfer the common user name to the DockerEngine, another command needs to be written to call these four methods. Other parameters are introduced according to the requirements of the users, for example, when Dockerrrun requests, a mounted directory needs to be introduced through a-v parameter, and a device number is introduced through a-d parameter.
In the method, the user can manage the container of the user only by executing the four methods, and the root can see the information of all users and operate the containers of all common users by screening the scripts.
Fig. 2 is a block diagram of an apparatus for responding to a user request in an application container engine according to the present invention. The apparatus shown in fig. 2 comprises:
an obtaining module 201, which obtains a user type of a user after receiving a Docker management request from the user;
a judging module 202, configured to judge whether a user type of the user is an ordinary user;
the authorization module 203 is configured to grant, according to a preset management policy, an authority of the user to manage the Docker if the user type of the user is a common user;
the response module 204 is configured to respond to a management request of the Docker of the user after the user acquires the right to manage the Docker.
In an embodiment of the apparatus provided in the present invention, the response module 204 includes:
the first output unit is used for outputting the list information of the mirror image file after receiving a management request of a user for establishing a container;
a receiving unit, configured to receive a target image file selected by the user from the list information;
and the establishing unit is used for establishing a container of the target image file so as to respond to the management request for establishing the container, and recording the identification information of the container.
In an embodiment of the apparatus provided by the present invention, the apparatus further comprises:
and the recording module is used for recording the corresponding relation between the identifier of the container and at least one of the following information after the container is established, wherein the information comprises user information, a container storage address, time information and a mirror image name.
In an embodiment of the apparatus provided in the present invention, the response module 204 includes:
the first acquisition unit is used for acquiring user information in a management request after receiving the management request of a user query container;
the first searching unit is used for searching the container identifier corresponding to the user information according to the corresponding relation between the pre-stored user information and the container identifier;
and the second output unit is used for outputting the information of the container corresponding to the container identifier.
In an embodiment of the apparatus provided in the present invention, the response module 204 includes:
the second acquisition module is used for acquiring user information, identification information of the container and identification information of the changed mirror image file in the management request after receiving the management request of changing the mirror image file of the existing container by the user;
the second searching unit is used for searching the identification information of the mirror image file corresponding to the user information according to the corresponding relation between the pre-stored user information and the mirror image file;
the judging unit is used for judging whether the identification information of the changed image file is in the identification information of the image file corresponding to the user information to obtain a judgment result;
and the loading unit is used for deleting the mirror image file in the container corresponding to the container identifier and loading the mirror image corresponding to the identifier information of the changed mirror image file if the judgment result is that the mirror image file is not in the container.
The device provided by the embodiment of the invention authorizes the common user by identifying and judging the user type, provides guarantee for responding the management request of the Docker of the user, solves the authority problem and improves the application range of the Docker.
It will be understood by those of ordinary skill in the art that all or part of the steps of the above embodiments may be implemented using a computer program flow, which may be stored in a computer readable storage medium and executed on a corresponding hardware platform (e.g., system, apparatus, device, etc.), and when executed, includes one or a combination of the steps of the method embodiments.
Alternatively, all or part of the steps of the above embodiments may be implemented by using an integrated circuit, and the steps may be respectively manufactured as an integrated circuit module, or a plurality of the blocks or steps may be manufactured as a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The devices/functional modules/functional units in the above embodiments may be implemented by general-purpose computing devices, and they may be centralized on a single computing device or distributed on a network formed by a plurality of computing devices.
Each device/function module/function unit in the above embodiments may be implemented in the form of a software function module and may be stored in a computer-readable storage medium when being sold or used as a separate product. The computer readable storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims (8)

1. A method of responding to user requests in an application container engine, comprising:
after a Docker management request of a user is received, acquiring the user type of the user;
judging whether the user type of the user is a common user or not;
if the user type of the user is a common user, granting the user the authority of managing Docker according to a preset management strategy;
after the user acquires the authority of managing the Docker, responding to the management request of the Docker of the user;
wherein the responding to the management request of the user's Docker includes:
when a management request of a user for changing the mirror image file of an existing container is received, acquiring user information, identification information of the container and identification information of the changed mirror image file in the management request;
searching identification information of the image file corresponding to the user information according to a corresponding relation between the pre-stored user information and the image file;
judging whether the identification information of the changed image file is in the identification information of the image file corresponding to the user information to obtain a judgment result;
and if the judgment result is that the image file is not in the storage device, deleting the image file in the storage device corresponding to the storage device identification, and loading the image corresponding to the identification information of the changed image file.
2. The method of claim 1, wherein responding to the management request of the user's Docker comprises:
after receiving a management request of a user for establishing a container, outputting list information of a mirror image file;
receiving a target image file selected from the list information by the user;
and establishing a container of the target image file to respond to the management request for establishing the container, and recording the identification information of the container.
3. The method of claim 2, further comprising:
after the container is established, recording the corresponding relation between the identifier of the container and at least one of the following information, wherein the information comprises user information, a container storage address, time information and a mirror image name.
4. The method of claim 3, wherein responding to the management request of the user's Docker comprises:
after receiving a management request of a user for inquiring a container, acquiring user information in the management request;
searching a container identifier corresponding to user information according to a corresponding relation between the pre-stored user information and the container identifier;
and outputting the information of the container corresponding to the container identification.
5. An apparatus for responding to a user request in an application container engine, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring the user type of a user after receiving a Docker management request of the user;
the judging module is used for judging whether the user type of the user is a common user or not;
the authorization module is used for granting the user the authority to manage the Docker according to a preset management strategy if the user type of the user is a common user;
the response module is used for responding to the management request of the Docker of the user after the user acquires the authority of managing the Docker;
wherein the response module comprises:
the second acquisition module is used for acquiring user information, identification information of the container and identification information of the changed mirror image file in the management request after receiving the management request of changing the mirror image file of the existing container by the user;
the second searching unit is used for searching the identification information of the mirror image file corresponding to the user information according to the corresponding relation between the pre-stored user information and the mirror image file;
the judging unit is used for judging whether the identification information of the changed image file is in the identification information of the image file corresponding to the user information to obtain a judgment result;
and the loading unit is used for deleting the mirror image file in the container corresponding to the container identifier and loading the mirror image corresponding to the identifier information of the changed mirror image file if the judgment result is that the mirror image file is not in the container.
6. The apparatus of claim 5, wherein the response module comprises:
the first output unit is used for outputting the list information of the mirror image file after receiving a management request of a user for establishing a container;
a receiving unit, configured to receive a target image file selected by the user from the list information;
and the establishing unit is used for establishing a container of the target image file so as to respond to the management request for establishing the container, and recording the identification information of the container.
7. The apparatus of claim 6, further comprising:
and the recording module is used for recording the corresponding relation between the identifier of the container and at least one of the following information after the container is established, wherein the information comprises user information, a container storage address, time information and a mirror image name.
8. The apparatus of claim 6, wherein the response module comprises:
the first acquisition unit is used for acquiring user information in a management request after receiving the management request of a user query container;
the first searching unit is used for searching the container identifier corresponding to the user information according to the corresponding relation between the pre-stored user information and the container identifier;
and the second output unit is used for outputting the information of the container corresponding to the container identifier.
CN201710958639.4A 2017-10-16 2017-10-16 Method and apparatus for responding to user request in application container engine Active CN107766707B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710958639.4A CN107766707B (en) 2017-10-16 2017-10-16 Method and apparatus for responding to user request in application container engine

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710958639.4A CN107766707B (en) 2017-10-16 2017-10-16 Method and apparatus for responding to user request in application container engine

Publications (2)

Publication Number Publication Date
CN107766707A CN107766707A (en) 2018-03-06
CN107766707B true CN107766707B (en) 2020-02-04

Family

ID=61268699

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710958639.4A Active CN107766707B (en) 2017-10-16 2017-10-16 Method and apparatus for responding to user request in application container engine

Country Status (1)

Country Link
CN (1) CN107766707B (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109376525B (en) * 2018-09-14 2020-11-03 网宿科技股份有限公司 Prompting method of Linux server, Linux server and computer readable storage medium
CN112148419B (en) * 2019-06-28 2024-01-02 杭州海康威视数字技术股份有限公司 Mirror image management method, device and system in cloud platform and storage medium
CN111880832A (en) * 2020-08-03 2020-11-03 上海嗨酷强供应链信息技术有限公司 Mirror image management method based on docker containerization technology

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105160269A (en) * 2015-08-13 2015-12-16 浪潮电子信息产业股份有限公司 Method and apparatus for accessing data in Docker container
CN106020930A (en) * 2016-05-13 2016-10-12 深圳市中润四方信息技术有限公司 Application container based application management method and system
CN106528224A (en) * 2016-11-03 2017-03-22 腾讯科技(深圳)有限公司 Content updating method and system for Docker container, and server
CN106845183A (en) * 2017-01-24 2017-06-13 郑州云海信息技术有限公司 A kind of application container engine management method and system
CN106897147A (en) * 2017-02-24 2017-06-27 郑州云海信息技术有限公司 A kind of application container engine container resource regulating method and device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105160269A (en) * 2015-08-13 2015-12-16 浪潮电子信息产业股份有限公司 Method and apparatus for accessing data in Docker container
CN106020930A (en) * 2016-05-13 2016-10-12 深圳市中润四方信息技术有限公司 Application container based application management method and system
CN106528224A (en) * 2016-11-03 2017-03-22 腾讯科技(深圳)有限公司 Content updating method and system for Docker container, and server
CN106845183A (en) * 2017-01-24 2017-06-13 郑州云海信息技术有限公司 A kind of application container engine management method and system
CN106897147A (en) * 2017-02-24 2017-06-27 郑州云海信息技术有限公司 A kind of application container engine container resource regulating method and device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
我们为什么不允许非root用户在CentOS直接运行;刘凯;《http://cloud.51cto.com/art/201508/488478.htm》;20150817;第1-4页 *
解决普通用户无法使用docker命令的问题;过去的我;《https://blog.csdn.net/aca_jingru/article/details/51943083》;20160718;第1页 *

Also Published As

Publication number Publication date
CN107766707A (en) 2018-03-06

Similar Documents

Publication Publication Date Title
CN109873804A (en) Service identification method, device, equipment and the readable storage medium storing program for executing of Behavior-based control
CN109766699A (en) Hold-up interception method and device, storage medium, the electronic device of operation behavior
CN107766707B (en) Method and apparatus for responding to user request in application container engine
CN108628658A (en) A kind of licence managing method and device of container
CN111756621A (en) Method and device for managing data of group users and maintaining instant messaging group
CN108027828A (en) It is synchronous with the trust instrument of stateless synchronization node
CN104573497B (en) A kind for the treatment of method and apparatus of startup item
CN104462937B (en) Operating system peripheral access permission control method based on users
CN104239797B (en) Active defense method and device
CN112527489A (en) Task scheduling method, device and equipment and computer readable storage medium
CN109992956A (en) The processing method and relevant apparatus of the security strategy of container
CN103701653B (en) The processing method of a kind of interface hot plug configuration data and network configuration server
JP6104447B1 (en) Program operation monitoring control device, distributed object generation management device, program, and program operation monitoring system
CN115150419B (en) Configuration and access method and system for hybrid cloud object storage
WO2018108423A1 (en) System and method for user authorization
CN107566375B (en) Access control method and device
CN110210241A (en) A kind of data desensitization method and device
CN114244568B (en) Security access control method, device and equipment based on terminal access behavior
CN104281488A (en) Implementation method and system of server engine
CN110210191A (en) A kind of data processing method and relevant apparatus
CN113377499A (en) Virtual machine management method, device, equipment and readable storage medium
CN111324799B (en) Search request processing method and device
CN112084021A (en) Interface configuration method, device and equipment of education system and readable storage medium
US9286305B2 (en) Virtual storage gate system
CN110046510A (en) Data migration method, device and system across cloud

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
TA01 Transfer of patent application right

Effective date of registration: 20191227

Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province

Applicant after: Suzhou Wave Intelligent Technology Co., Ltd.

Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601

Applicant before: Zhengzhou Yunhai Information Technology Co. Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant