Container-based private server architecture and a construction and visualization method thereof

Abstract

The invention provides a container-based private server architecture and a construction and visualization method thereof. The private server architecture comprises a core service module, a core service module providing a user interface and a token service module. Registry module for storing Docker images; And a database module, wherein the database module stores user rights; The user interface helps users to manage Docker image on Registry module through graphical interface. When a user pulls an image from or uploads an image to a Registry module via the user interface, The Registry module points to a token service module, the token service module issues a token for the command according to the user rights, and the Registry module decrypts and verifies the token through the public key to display the corresponding content on the user interface according to the user rights. Based on this, the architecture of the invention can effectively reduce complexity, improve expansibility, and conveniently support application deployment and integration of a system distributed environment.

Description

technical field [0001] The present invention generally relates to the field of computer technology, and more specifically, relates to a container-based private server architecture and its construction and visualization methods. Background technique [0002] Docker is an open source application container engine that allows developers to package their applications and dependencies into a portable container and then distribute them to Linux machines. Docker supports a variety of ways to create container image storage. In addition to open source or public projects that need to use the default public warehouse, there are also save / load methods implemented by Docker commands that are suitable for customizing certain things. There are two types of existing private server warehouses: the first is that Docker officially provides the Docker Hub website as a public centralized warehouse; the second is to create and access the private server warehouse of Docker Hub locally, give relevan...

AI Technical Summary

Problems solved by technology

[0003] However, the above two solutions have the following disadvantages: 1. The speed of the first method is often very slow. When connecting to an external network, if the server is located in a foreign country, the access in China will be very slow, which will affect the efficiency; 2. The second method It can be created locally, but there is no relevant management interface provided. It needs to use a unique http rest request to access, modify related configurations, and perform CRUD (Create Read Update and Delete) operations on the image; 3 .There is no role-based access control (Role Based Access Control, RBAC), basically only administrator privileges or people with relevant certificates can access; 4. There is no audit log (Audit logging), and it is impossible to check who modified the mirror warehouse Mirroring and related log auditing; 5. It is inconvenient for ordinary people to operate, and people who do not understand technology may not be able to operate

Images