WO2018233370A1

WO2018233370A1 - Method, system, device, and computer readable storage medium for synchronizing image

Info

Publication number: WO2018233370A1
Application number: PCT/CN2018/083947
Authority: WO
Inventors: 刘俊杰
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-06-21
Filing date: 2018-04-20
Publication date: 2018-12-27
Also published as: CN107247793A; CN107247793B

Abstract

The present application discloses a method for synchronizing an image and a system, a device, and a computer readable storage medium for synchronizing an image of a Docker image registry. In the method for synchronizing an image, when a cloud district registry receives an image pushed by an available district registry, a cloud district control unit is notified that an image event has been received. Then, the cloud district control unit analyzes the image event. If it is determined that the image event needs to be synchronized, the cloud district registry is controlled to synchronize the image to a corresponding available district registry. In the present application, by configuring control units and registries in a cloud district and each available district and monitoring the events of Docker image registry, images of the cloud district and each available district are synchronized, such that the issue of Docker image real-time synchronization is resolved.

Description

Mirror synchronization method, system, device and computer readable storage medium

This application claims the priority of the Chinese Patent Application filed on June 21, 2017, the Chinese Patent Office, the application number is 201710473796.6, and the invention is entitled "Mirror Image Synchronization Method and Mirror Synchronization System of Docker Image Warehouse", the entire contents of which are incorporated by reference. In the application.

Technical field

The present application relates to the field of Docker technology, and specifically relates to a mirror synchronization method of a Docker image repository, a mirror synchronization system, a device, and a computer readable storage medium.

Background technique

Docker (Docker Is an open source application container engine that allows developers to package their applications and dependencies into a portable container and then publish them to any popular Linux On the machine, virtualization can also be implemented. The container technology provided allows several containers to be run on the same host or virtual machine, each container being a separate virtual environment or application.

Container from Docker Mirroring, which can be generated by the user or submitted by the running container. After the image is generated, it can be pushed to the image repository for saving, or pulled from the mirror repository. Go to the local to run the container.

Docker provides an official image repository (Docker hub), while allowing users to build their own private image repository (private Registry). For most organizations and organizations, it is necessary to use a private image repository to protect the mirrored content and use of the repository.

Mirrors are stored in the file system as tiered storage. Different images may share some layers to save storage space. For warehouse construction involving multi-regional user access, mirror synchronization is a must-have when unified management of the image is required to ensure that the scope of the image used by the user is not limited to a certain area.

Mirror synchronization can be implemented by multiple schemes, one of which is shared storage, that is, a registry of multiple areas mounts a shared network storage disk, so that each time a mirror is pushed to a certain area of the registry. All the warehouses are immediately synchronized. However, sometimes the multi-region registry cannot share storage, and the networks between the regions cannot access each other, that is, the regions are isolated.

When using a Docker image in a multi-tenant environment, users under the tenant are typically restricted to access only the mirrored repository deployed in the public service area of each Availability Zone. For public mirroring, you need to synchronize in the mirrored warehouse of each available area; for private mirrors inside the tenant, you also need to synchronize the mirror to each available area. For the user, the images in each available area that they can see should be consistent, while the cloud storage of each available area cannot be shared across areas, and the mirrored events cannot be distributed to other available areas, so the shared storage cannot be used. The way to achieve synchronization, and only use real-time synchronization.

Therefore, the prior art has yet to be improved and developed.

Summary of the invention

In view of the above-mentioned deficiencies of the prior art, the present application provides a mirror synchronization method, a mirror synchronization system, a device, and a computer-readable storage medium of a Docker image warehouse, which mainly solve the problem that the existing Docker images cannot be synchronized in real time.

The technical solution adopted by the present application to solve the technical problem is as follows:

A mirror synchronization method for a Docker image repository, the image synchronization method comprising the following steps:

When the cloud management area warehouse receives the image pushed by the warehouse of a certain available area, the cloud control area control unit is notified to receive the mirroring event;

The cloud management area control unit resolves the mirror event. When it is determined that the mirror event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.

In addition, to achieve the above object, the present application further provides a mirror synchronization system of a Docker image warehouse, where the image synchronization system includes:

The cloud management area warehouse is configured to notify the cloud management area control unit to receive the mirroring event when receiving the image pushed by the warehouse of an available area;

The cloud management area control unit is configured to parse the mirroring event. When it is determined that the mirroring event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.

In addition, in order to achieve the above object, the present application further provides a mirror synchronization device of a Docker image repository, wherein the mirror synchronization device of the Docker image repository includes a memory, a processor, and a storage on the memory and can be The image synchronization program of the Docker image repository running on the processor, the mirror synchronization program of the Docker image repository being executed by the processor to implement the steps of the image synchronization method of the Docker image repository described above.

In addition, in order to achieve the above object, the present application further provides a computer readable storage medium, wherein the computer readable storage medium stores a mirror synchronization program of a Docker image repository, and a mirror synchronization program of the Docker image repository The steps of implementing the image synchronization method of the Docker image repository described above when executed by the processor.

The present application discloses a mirror synchronization method and a mirror synchronization system of a Docker image warehouse. When the image synchronization method first receives a mirror image pushed by an available area warehouse from the cloud management area warehouse, the cloud control area control unit is notified to receive the mirroring event; The pipe area control unit resolves the mirror event. When it is determined that the mirror event needs to be synchronized, the cloud control area warehouse is controlled to synchronize the image to the corresponding available area warehouse. This application solves the problem of Docker by setting up a control unit and a warehouse in the cloud management area and each available area, and monitoring the events of the Docker image warehouse to realize the mirror synchronization of the cloud management area and each available area. Mirror real-time synchronization issues.

DRAWINGS

1 is a flow chart of a preferred embodiment of a method for mirror synchronization of a Docker image repository provided by the present application.

2 is a flow chart of a preferred embodiment of step S200 in the image synchronization method of the Docker image repository provided by the present application.

FIG. 3 is a schematic diagram of a first application embodiment in a mirror synchronization method of a Docker image repository provided by the present application.

4 is a schematic diagram of a second application embodiment in a mirror synchronization method of a Docker image repository provided by the present application.

FIG. 5 is a schematic diagram of a third application embodiment in a mirror synchronization method of a Docker image repository provided by the present application.

6 is a functional block diagram of a mirror synchronization system of the Docker image repository of the present application.

FIG. 7 is a functional block diagram of a cloud management area control unit in a mirror synchronization system of a Docker image warehouse of the present application.

Detailed ways

In order to make the objects, technical solutions, and advantages of the present application more clear and clear, the present application will be further described in detail below with reference to the accompanying drawings. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

Please refer to FIG. 1 , which is a flowchart of a preferred embodiment of a mirror synchronization method of a Docker image repository provided by the present application. As shown in FIG. 1, the image synchronization method of the Docker image warehouse described in the preferred embodiment of the present application is as follows:

When the S100 and the cloud management area warehouse receive the image pushed by the warehouse of an available area, the cloud control area control unit is notified to receive the mirroring event.

In this embodiment, a control unit and a warehouse are disposed in the cloud management area and each available area, and the cloud management area is one, and the available area is several, which is used to manage the mirror of each available area.

Preferably, before step S100, the method further comprises: controlling, by an available area control unit, the available area warehouse to push the image to the cloud management area warehouse.

During specific implementation, the user terminal pushes a mirror to the available area warehouse, triggers the area warehouse to notify the available area control unit to receive the mirroring event, and the available area control unit resolves the mirroring event to determine whether the mirroring event is a pull event or a push event. If it is a push event, the API interface of the available area warehouse is called (Application Programming Interface, the application programming interface) synchronizes the image to the cloud management area repository.

In step S200, the cloud management area control unit parses the image event. When it is determined that the mirror event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.

In this embodiment, when the cloud management area control unit determines that the mirroring event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse, thereby realizing the synchronization of each available area image and the cloud management area.

Please refer to FIG. 2 , which is a flowchart of a preferred embodiment of step S200 in the image synchronization method of the Docker image repository provided by the present application.

As shown in FIG. 2, the step S200 includes:

Step S201: The cloud management area control unit parses the mirroring event, and determines whether the mirroring event is a pull event or a push event;

Step S202: If the mirroring event is a push event, determine that the mirroring event needs to be synchronized, and call the API interface of the cloud management area warehouse to synchronize the image to the corresponding available area warehouse. When the mirroring event is a pull event, or the mirror exists in the cloud management area warehouse, no synchronization operation is performed.

In a specific implementation, the step S202 includes:

S2021: If the mirroring event is a push event, determine that the mirroring event needs to be synchronized. When the mirroring event is a pull event, or the mirror exists in the cloud management area warehouse, no synchronization operation is performed.

S2022: If the mirror event is a push event, parse the source of the mirror event to obtain an available area warehouse that pushes the image. In the cloud management area control unit, the distribution task of the source available area warehouse is eliminated to avoid synchronous loopback.

S2023: Calling the API interface of the cloud management area warehouse to synchronize the image to each available area warehouse except the free area warehouse pushed to the mirror. When the synchronous mirroring event occurs, the image is not distributed to the free area warehouse that pushes the image.

In order to better understand the technical solution of the present application, the first application embodiment is exemplified in detail for the mirror synchronization method of the Docker image warehouse of the present application:

The cloud management area is a centralized management area, and each available area can be set at different locations. For example, the A free area is set in Shanghai, the B free area is set in Beijing, and the C free area is set in Shenzhen. The A Availability Zone, the B Availability Zone, and the C Availability Zone cannot communicate with each other. The A Availability Zone, the B Availability Zone, and the C Availability Zone can only communicate with the cloud management zone to perform push or pull mirror operations.

As shown in FIG. 3, the first application embodiment of the present application specifically includes:

In the first step, the image is pushed by the user terminal to the A Availability Zone Warehouse;

Step 2: After receiving the image, the A Availability Zone Warehouse notifies the A Availability Zone Control Unit to receive the mirroring event and store the image;

The third step, after the A Availability Zone Control Unit resolves the mirror event, and controls the A Availability Zone Warehouse to push the image to the cloud management area warehouse;

In the fourth step, when the cloud management area warehouse receives the image pushed by the A free area warehouse, the cloud control area control unit is notified to receive the mirroring event;

The fifth step, the cloud management area control unit resolves the mirror event, and when the mirror event is determined to be a push event, the cloud control area warehouse is controlled to synchronize the image to the A free area warehouse, the B free area warehouse, and the C free area warehouse, and when the mirror event is determined to be pulled The mirror event is not processed when the event is fetched.

In order to avoid wasting network resources, the application also adopts a loopback prevention and filtering mechanism. The step S202 further includes: if the mirroring event is a push event, parsing the source of the mirroring event; when the mirroring event is synchronous, the mirroring is not distributed. The free area repository for the image to be pushed.

In this embodiment, when determining the source of the mirror event, the IP of the available area warehouse of the push image is identified, so that the event push source can be accurately determined.

Further, after step S200, the image synchronization method of the Docker image repository of the present application further includes:

Step S300: When each available area warehouse receives the image, notify the available area control unit to receive the mirroring event;

Step S400: The available area control unit determines whether the mirroring event is from a cloud management area, and if so, the available area warehouse will not continue to distribute the image.

By setting a loopback prevention and filtering mechanism in the cloud management area and each available area, the application prevents the mirror push event from being infinitely looped back, thereby effectively saving network resources.

In order to facilitate a better understanding of the loopback mechanism of the present application, a second application embodiment is exemplified herein to describe the mirror synchronization method of the Docker image repository of the present application in detail:

As shown in FIG. 4, the second application embodiment of the present application specifically includes:

In the first step, the A Availability Zone Warehouse pushes the image to the cloud management area warehouse;

In the second step, when the cloud management area warehouse receives the image pushed by the A free area warehouse, the cloud control area control unit is notified to receive the mirroring event;

The third step, the cloud management area control unit resolves the mirror event. When the mirror event is determined to be a push event, and it is determined that the mirror event needs to be synchronized, the source of the push event is analyzed as the A free area warehouse, and the distribution task of the A free area warehouse is analyzed. Eliminate

In the fourth step, the cloud management area control unit sends the distribution task to the cloud management area warehouse;

In the fifth step, the cloud management area warehouse distributes the image to the B free area warehouse and the C free area warehouse;

After the sixth step, the B Availability Zone Warehouse and the C Availability Zone Warehouse receive the image, the notification B may receive the mirroring event by using the control unit and the C available control unit;

The seventh step, B, the control unit and the C available control unit analyze the source of the mirror event as the cloud management area, delete the current push task, no longer distribute, and avoid loopback (ie, avoid pushing the mirror loop).

In the mirror synchronization, there may be a case where the synchronization fails (for example, when the mirror synchronization occurs, the network termination abnormality causes the mirror synchronization to fail), in order to improve the accuracy of the mirror synchronization, in the mirror synchronization method of the Docker image warehouse of the present application. The cloud management area warehouse periodically pushes all the images to the available area warehouses. During specific implementation, the cloud management area control unit controls the cloud management area warehouse to push the image to each available area at two o'clock every morning.

In order to avoid the mirror synchronization repetition, during the periodic synchronization, the cloud management unit calls the API interface of the source mirror warehouse to push the image to the corresponding available area warehouse, and interacts with the available area warehouse to detect whether the available area warehouse has the pushed image. When the detection image exists, the image is aborted.

In a more complex network environment, there are multiple free area warehouses in one available area, and the load is balanced. Each available area warehouse provides a VIP. (Very Important Person, VIP) and port, the area targeting the Availability Zone should push the image to the vip And the port, and when judging the loopback, you should check whether the event source is the real ip and port of the available area warehouse.

Therefore, when there are multiple warehouses in each available area, the cloud management area control unit controls the cloud management area warehouse to synchronize the image to the corresponding available area warehouse, specifically: the cloud management area control unit identifies the real IP of the mirror event, and determines the real IP. Whether it matches the real IP of an available area warehouse, if it is, the distribution task of the available area warehouse is removed, and the image is not pushed to the available area warehouse.

Specifically, when there are multiple warehouses in an area, in order to load balance the warehouses, the present application uses all the warehouses in each area to provide a vip and a port, and when other areas push the image to the area, the vip and the port are used. Issued. For each available area, the distribution target is only the cloud management area mirror warehouse VIP and port. When the control unit receives the mirror push event, the real-time IP of the mirror event source is used to query whether the IP is the real IP address of the cloud management area mirror warehouse. First, if the cloud management area mirror warehouse VIP is removed from the current distribution task, the target of the current distribution task is empty, and the synchronization mirror is no longer continued.

For the cloud management area, the distribution target includes the VIP and port of each available area mirror warehouse. When the cloud control area control unit receives the mirror push event, according to the real IP of the mirror event source, it is queried whether the IP is the real state of an available area mirror warehouse. One of the IPs, if it is, the VIP of the regional mirror warehouse is removed from the current distribution task. At this time, the target of the current distribution task is another available area mirror warehouse, and the source area is no longer synchronized downward, but is synchronized. Other areas. In load balancing, the same mirror push request is only processed by one of the multiple warehouses, and multiple warehouses share the storage, so any one of them is treated equally, due to control unit control.

In order to facilitate a better understanding of the loopback mechanism in the multi-warehouse of each area, the third application embodiment is described herein to describe the mirror synchronization method of the Docker image warehouse of the present application in detail:

As shown in FIG. 5, the third application embodiment of the present application specifically includes:

The first step, C Availability Zone Warehouse 1 pushes the image to the cloud management area warehouse VIP and port;

The second step, the cloud management area warehouse VIP and port will be sent to the cloud management area warehouse 2 for processing the mirror push request;

The third step, after receiving the push image, the cloud management area warehouse 2 notifies the cloud management area control unit;

The fourth step, after receiving the mirroring event, the cloud management unit control unit analyzes the real IP of the source of the push mirror event as the C available area warehouse 1, and removes the distribution task of the C available area;

The fifth step, the cloud management area control unit controls the cloud management area warehouse 2 to push the image to the free area warehouse VIP and the port and the B available area warehouse VIP and port through the cloud management area warehouse VIP and port.

In addition, a storage module is also provided in the control unit of the cloud management area for storing the contents of the warehouse and the mirror to avoid data loss caused by abnormal conditions. Specifically, when the cloud management unit receives the push event, the specific information of the image is saved in the storage module.

The public image can be synchronized in the mirrored warehouse of each available area in time; the private image inside the tenant can be synchronized to each available area in time to ensure that the user can view the public image and the user under the tenant in any available area. Private images inside the tenant are inaccessible and indiscriminate.

The application also provides a mirror synchronization system of a Docker image warehouse. As shown in FIG. 6, the device includes: a cloud management area warehouse 11 and a cloud management area control unit 12, and the cloud management area warehouse 11 communicates with the cloud management area control unit 12. The cloud control area control unit 12 notifies the cloud management area control unit 12 of receiving the mirroring event when receiving the image pushed by the available area warehouse. The cloud management area control unit 12 is configured to parse the mirroring event. When it is determined that the mirroring event needs to be synchronized, the cloud management area warehouse 11 is controlled to synchronize the image to the corresponding available area warehouse. For details, please refer to the corresponding embodiment of the above method.

The image synchronization system of the Docker image repository of the present application further includes an Availability Zone Warehouse 21 and an Availability Zone Control Unit 22, which is connected to the Availability Zone Control Unit 22. The available area is a plurality. The available area control unit is configured to control the available area warehouse to push the image to the cloud management area warehouse.

In a specific implementation, the user terminal pushes a mirror image to the available area warehouse 21, triggering the area warehouse 21 to notify the available area control unit 22 to receive the mirroring event, and the available area control unit 22 resolves the mirroring event to determine that the mirroring event is a pull event. Or push event, if it is a push event, call the API interface of the available area warehouse 21 to push the image to the cloud management area warehouse.

The available area warehouse is configured to notify the available area control unit to receive the mirroring event when receiving the image. The available area control unit is further configured to determine whether the mirroring event is from a cloud management area, and if so, the available area storage will not continue to distribute the image, thereby preventing image loopback.

When judging the source of the mirror event, the source of the event push can be accurately determined by identifying the IP of the available area warehouse of the push image. Referring to FIG. 5, when there are multiple warehouses in each available area, the cloud management area control unit is further configured to identify the real IP of the mirroring event, and determine whether the real IP matches the real IP of an available area warehouse. If so, the image is not pushed to the free area repository. For details, please refer to the corresponding embodiment of the above method.

Referring to FIG. 7 , in the specific implementation, the cloud management area control unit 12 includes: a parsing subunit 121 and a mirror sync subunit 122.

The parsing sub-unit 121 is configured to parse the mirroring event and determine whether the mirroring event is a pull event or a push event. The mirror synchronization sub-unit 122 is configured to mirror the event as a push event, determine that the mirror event needs to be synchronized, and then invoke the API interface of the cloud management area warehouse to synchronize the image to each corresponding available area warehouse.

The parsing sub-unit 121 is specifically configured to: when the mirroring event is a push event, determine that the mirroring event needs to be synchronized, parse the source of the mirroring event to obtain an available area warehouse that pushes the mirror. The image synchronization sub-unit 122 is specifically configured to invoke an API interface of the cloud management area warehouse to synchronize the image to other available area warehouses other than the available area warehouse pushed to the image. For details, please refer to the corresponding embodiment of the above method.

In a further embodiment, the cloud management area control unit 12 also controls the cloud management area warehouse to periodically push all the images to the available area warehouses to avoid mirror synchronization, and when the mirror synchronization fails due to network interruption, etc., it does not affect. Under the premise of the business, the accuracy of image synchronization is further ensured. For details, please refer to the corresponding embodiment of the above method.

In summary, the present application solves the problem of Docker by setting up a control unit and a warehouse in the cloud management area and each available area, and monitoring the events of the Docker image warehouse to realize mirror synchronization between the cloud management area and each available area. Mirror real-time synchronization issues. The private image inside the tenant can also be synchronized to each available area in time, so that in any available area, the user has no indiscriminate access to the public image and the user under the tenant for the private image inside the tenant.

In addition, the embodiment of the present application further provides a mirror synchronization system of a Docker image warehouse, where the image synchronization system includes:

Further, the image synchronization system of the Docker image warehouse further includes:

The available area control unit is configured to control the available area warehouse to push the image to the cloud management area warehouse.

Further, the cloud management area control unit is further configured to parse the mirroring event, and determine whether the mirroring event is a pull event or a push event;

If the mirroring event is a push event, it is determined that the mirroring event needs to be synchronized, and the API interface of the cloud management area warehouse is called to synchronize the image to the corresponding available area warehouse.

Further, the cloud management area control unit is further used for

If the mirroring event is a push event, it is determined that the mirroring event needs to be synchronized;

Parsing the source of the mirrored event to obtain an available area repository that pushes the image;

Call the API interface of the cloud management area repository to synchronize the image to each free area warehouse except the free area warehouse pushed to the image.

The available area warehouse is configured to notify the available area control unit to receive the mirroring event when receiving the image;

The available area control unit is further configured to determine whether the mirroring event is from a cloud management area, and if so, the available area warehouse will not continue to distribute the image.

Further, the cloud management area control unit is further configured to identify the real IP of the mirror event, determine whether the real IP matches the real IP of the available area warehouse, and if not, push the image to the available area warehouse.

In addition, the embodiment of the present application further provides a mirror synchronization device of a Docker image repository, where the mirror synchronization device of the Docker image repository includes a memory, a processor, and a Docker stored on the memory and executable on the processor. A mirror synchronization program of the mirror repository, the mirror synchronization program of the Docker image repository being executed by the processor to implement the steps of the image synchronization method of the Docker image repository as described above.

In addition, the embodiment of the present application further provides a computer readable storage medium, where the image synchronization storage program stores a mirror synchronization program of a Docker image repository, and the image synchronization program of the Docker image repository is implemented by the processor. Steps to the image synchronization method of the Docker image repository

Certainly, those skilled in the art can understand that all or part of the processes in the foregoing embodiments can be implemented by a computer program to instruct related hardware (such as a processor, a controller, etc.), and the program can be stored in one. In a computer readable storage medium, the program, when executed, may include the processes of the various method embodiments as described above. The storage medium described therein may be a memory, a magnetic disk, an optical disk, or the like.

It should be understood that the application of the present application is not limited to the above-described examples, and those skilled in the art can make modifications and changes in accordance with the above description, all of which are within the scope of the appended claims.

Claims

A mirror synchronization method for a Docker image repository, characterized in that the image synchronization method comprises the following steps:

When the cloud management area warehouse receives the image pushed by the warehouse of a certain available area, the cloud control area control unit is notified to receive the mirroring event;

The cloud management area control unit resolves the mirror event. When it is determined that the mirror event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.
The image synchronization method of the Docker image warehouse according to claim 1, wherein the cloud management area warehouse notifies the cloud management area control unit of the mirror event before receiving the image event pushed by the available area warehouse. include:

The available area warehouse controls the available area warehouse to push the image to the cloud area warehouse.
The image synchronization method of the Docker image warehouse according to claim 1, wherein the cloud management area control unit parses the image event, and when the image event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse. The steps include:

The cloud management area control unit parses the mirroring event, and determines whether the mirroring event is a pull event or a push event;

If the mirror event is a push event, it is determined that the mirror event needs to be synchronized, and the API interface of the cloud management area warehouse is called to synchronize the image to the corresponding available area warehouse.
The mirror synchronization method of the Docker image warehouse according to claim 3, wherein if the mirror event is a push event, it is determined that the mirror event needs to be synchronized, and the API interface of the cloud management area warehouse is called to synchronize the image to the corresponding available area warehouse. The steps include:

If the mirroring event is a push event, it is determined that the mirroring event needs to be synchronized;

Parsing the source of the mirrored event to obtain an available area repository that pushes the image;

Call the API interface of the cloud management area repository to synchronize the image to each free area warehouse except the free area warehouse pushed to the image.
The image synchronization method of the Docker image warehouse according to claim 1, wherein the cloud management area control unit parses the image event, and when the image event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse. After the steps, it also includes:

When each available area warehouse receives the image, it notifies the available area control unit to receive the mirroring event;

The availability zone control unit determines whether the mirroring event originates from a cloud management zone, and if so, the free zone repository will no longer continue to distribute the image.
The image synchronization method of the Docker image warehouse according to claim 2, wherein the cloud management area control unit parses the image event, and when the image event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse. After the steps, it also includes:

When each available area warehouse receives the image, it notifies the available area control unit to receive the mirroring event;

The availability zone control unit determines whether the mirroring event originates from a cloud management zone, and if so, the free zone repository will no longer continue to distribute the image.
The image synchronization method of the Docker image warehouse according to claim 3, wherein the cloud management area control unit parses the image event, and when the image event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse. After the steps, it also includes:

When each available area warehouse receives the image, it notifies the available area control unit to receive the mirroring event;

The availability zone control unit determines whether the mirroring event originates from a cloud management zone, and if so, the free zone repository will no longer continue to distribute the image.
The image synchronization method of the Docker image warehouse according to claim 4, wherein the cloud management area control unit resolves the mirror event, and when the mirror event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse. After the steps, it also includes:

When each available area warehouse receives the image, it notifies the available area control unit to receive the mirroring event;

The availability zone control unit determines whether the mirroring event originates from a cloud management zone, and if so, the free zone repository will no longer continue to distribute the image.
The image synchronization method of the Docker image warehouse according to claim 1, wherein when the available areas have a plurality of warehouses, the cloud management unit control unit controls the cloud management area warehouse to synchronize the mirrors to the corresponding available area warehouses. :

The cloud management area control unit identifies the real IP of the mirror event, determines whether the real IP matches the real IP of an available area warehouse, and if so, does not push the image to the available area warehouse.
A mirror synchronization system of a Docker image warehouse, characterized in that the image synchronization system comprises:

The cloud management area warehouse is configured to notify the cloud management area control unit to receive the mirroring event when receiving the image pushed by the warehouse of an available area;

The cloud management area control unit is configured to parse the mirroring event. When it is determined that the mirroring event needs to be synchronized, the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.
The image synchronization system of the Docker image repository according to claim 10, further comprising:

The available area control unit is configured to control the available area warehouse to push the image to the cloud management area warehouse.
A mirror synchronization system for a Docker image repository according to claim 10, wherein

The cloud management area control unit is further configured to parse the mirroring event, and determine whether the mirroring event is a pull event or a push event;

If the mirroring event is a push event, it is determined that the mirroring event needs to be synchronized, and the API interface of the cloud management area warehouse is called to synchronize the image to the corresponding available area warehouse.
The image synchronization system of the Docker image warehouse according to claim 12, wherein the cloud management area control unit is further used for

If the mirroring event is a push event, it is determined that the mirroring event needs to be synchronized;

Parsing the source of the mirrored event to obtain an available area repository that pushes the image;

Call the API interface of the cloud management area repository to synchronize the image to each free area warehouse except the free area warehouse pushed to the image.
The image synchronization system of the Docker image repository according to claim 11, further comprising:

The available area warehouse is configured to notify the available area control unit to receive the mirroring event when receiving the image;

The available area control unit is further configured to determine whether the mirroring event is from a cloud management area, and if so, the available area warehouse will not continue to distribute the image.
The image synchronization system of the Docker image repository according to claim 12, further comprising:

The available area warehouse is configured to notify the available area control unit to receive the mirroring event when receiving the image;

The available area control unit is further configured to determine whether the mirroring event is from a cloud management area, and if so, the available area warehouse will not continue to distribute the image.
The image synchronization system of the Docker image repository according to claim 13, further comprising:

The available area warehouse is configured to notify the available area control unit to receive the mirroring event when receiving the image;

The available area control unit is further configured to determine whether the mirroring event is from a cloud management area, and if so, the available area warehouse will not continue to distribute the image.
The image synchronization system of the Docker image repository according to claim 14, further comprising:

The available area warehouse is configured to notify the available area control unit to receive the mirroring event when receiving the image;

The available area control unit is further configured to determine whether the mirroring event is from a cloud management area, and if so, the available area warehouse will not continue to distribute the image.
The mirror synchronization system of the Docker mirror warehouse according to claim 10, wherein the cloud management area control unit is further configured to identify a real IP of the mirror event, and determine whether the real IP is a real IP of an available area warehouse. Match, if not, push the image to the free area repository.
A mirror synchronization device of a Docker image repository, wherein the mirror synchronization device of the Docker image repository includes a memory, a processor, and a mirror of a Docker image repository stored on the memory and executable on the processor A synchronization program, the step of implementing the image synchronization method of the Docker image repository of claim 1 when the image synchronization program of the Docker image repository is executed by the processor.
A computer readable storage medium, wherein the computer readable storage medium stores a mirror synchronization program of a Docker image repository, and the image synchronization program of the Docker image repository is executed by the processor as claimed in claim 1. The steps of the mirror synchronization method of the Docker image repository.