WO2018233370A1 - Procédé, système, dispositif et support de stockage lisible par ordinateur de synchronisation d'une image - Google Patents

Procédé, système, dispositif et support de stockage lisible par ordinateur de synchronisation d'une image Download PDF

Info

Publication number
WO2018233370A1
WO2018233370A1 PCT/CN2018/083947 CN2018083947W WO2018233370A1 WO 2018233370 A1 WO2018233370 A1 WO 2018233370A1 CN 2018083947 W CN2018083947 W CN 2018083947W WO 2018233370 A1 WO2018233370 A1 WO 2018233370A1
Authority
WO
WIPO (PCT)
Prior art keywords
image
warehouse
event
cloud management
control unit
Prior art date
Application number
PCT/CN2018/083947
Other languages
English (en)
Chinese (zh)
Inventor
刘俊杰
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018233370A1 publication Critical patent/WO2018233370A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/178—Techniques for file synchronisation in file systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Definitions

  • 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.
  • 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.
  • 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.
  • a mirror synchronization method for a Docker image repository comprising the following steps:
  • the cloud management area warehouse 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.
  • the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.
  • 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.
  • the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • step S200 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.
  • FIG. 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.
  • FIG. 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.
  • FIG. 1 is a flowchart of a preferred embodiment of a mirror synchronization method of a Docker image repository provided by the present application.
  • the image synchronization method of the Docker image warehouse described in the preferred embodiment of the present application is as follows:
  • the cloud control area control unit 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.
  • 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.
  • 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.
  • 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.
  • step S200 the cloud management area control unit parses the image event.
  • the cloud management area warehouse is controlled to synchronize the image to the corresponding available area warehouse.
  • 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.
  • FIG. 2 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.
  • 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.
  • the step S202 includes:
  • 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.
  • 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.
  • the A free area is set in Shanghai
  • the B free area is set in Beijing
  • 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.
  • the first application embodiment of the present application specifically includes:
  • 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;
  • the cloud control area control unit is notified to receive the mirroring event
  • 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.
  • 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 is not distributed.
  • the IP of the available area warehouse of the push image is identified, so that the event push source can be accurately determined.
  • 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.
  • the application prevents the mirror push event from being infinitely looped back, thereby effectively saving network resources.
  • the second application embodiment of the present application specifically includes:
  • the A Availability Zone Warehouse pushes the image to the cloud management 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.
  • 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.
  • the cloud management area control unit sends the distribution task to the cloud management area warehouse
  • the cloud management area warehouse distributes the image to the B free area warehouse and the C free area warehouse;
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • VIP Very Important Person
  • 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.
  • 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.
  • the distribution target is only the cloud management area mirror warehouse VIP and port.
  • 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.
  • the distribution target includes the VIP and port of each available area mirror warehouse.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • the cloud management area warehouse 11 is controlled to synchronize the image to the corresponding available area warehouse.
  • 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.
  • 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.
  • 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.
  • the source of the event push can be accurately determined by identifying the IP of the available area warehouse of the push image.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the embodiment of 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.
  • 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 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.
  • 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;
  • 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 cloud management area control unit is further used for
  • the mirroring event is a push event, it is determined that the mirroring event needs to be synchronized
  • the image synchronization system of the Docker image warehouse further includes:
  • 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 warehouse further includes:
  • 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 warehouse further includes:
  • 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 warehouse further includes:
  • 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 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.
  • 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.
  • 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
  • a computer program to instruct related hardware (such as a processor, a controller, etc.), and the program can be stored in one.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un procédé de synchronisation d'une image et un système, un dispositif, et un support de stockage lisible par ordinateur de synchronisation d'une image d'un registre d'images Docker. Dans le procédé de synchronisation d'une image, lorsqu'un registre de district en nuage reçoit une image distribuée sélectivement par un registre de district disponible, il est notifié à une unité de commande de district en nuage qu'un événement d'image a été reçu. Ensuite, l'unité de commande de district en nuage analyse l'événement d'image. S'il est déterminé que l'événement d'image doit être synchronisé, le registre de district en nuage est commandé pour synchroniser l'image par rapport à un registre de district disponible correspondant. Dans la présente invention, en configurant des unités de commande et des registres d'un district en nuage et de chaque district disponible et en surveillant les événements de registre d'images Docker, des images du district en nuage et de chaque district disponible sont synchronisées, de sorte que le problème de la synchronisation d'images Docker en temps réel est résolu.
PCT/CN2018/083947 2017-06-21 2018-04-20 Procédé, système, dispositif et support de stockage lisible par ordinateur de synchronisation d'une image WO2018233370A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710473796.6 2017-06-21
CN201710473796.6A CN107247793B (zh) 2017-06-21 2017-06-21 Docker镜像仓库的镜像同步方法和镜像同步系统

Publications (1)

Publication Number Publication Date
WO2018233370A1 true WO2018233370A1 (fr) 2018-12-27

Family

ID=60019519

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/083947 WO2018233370A1 (fr) 2017-06-21 2018-04-20 Procédé, système, dispositif et support de stockage lisible par ordinateur de synchronisation d'une image

Country Status (2)

Country Link
CN (1) CN107247793B (fr)
WO (1) WO2018233370A1 (fr)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107247793B (zh) * 2017-06-21 2020-03-17 平安科技（深圳）有限公司 Docker镜像仓库的镜像同步方法和镜像同步系统
CN108200155A (zh) * 2017-12-29 2018-06-22 平安科技（深圳）有限公司 Docker镜像仓库的镜像同步方法和镜像同步系统
CN107948201B (zh) * 2017-12-29 2020-11-13 平安科技（深圳）有限公司 Docker镜像仓库的权限认证方法和系统
CN110099076A (zh) * 2018-01-29 2019-08-06 中兴通讯股份有限公司 一种镜像拉取的方法及其系统
WO2019165573A1 (fr) * 2018-02-27 2019-09-06 深圳中兴力维技术有限公司 Procédé, dispositif et système de synchronisation d'images basés sur un conteneur docker
CN110196679B (zh) * 2018-03-21 2023-01-17 腾讯科技（深圳）有限公司 分布式部署系统、对象管理方法、装置、介质及电子设备
CN109062663B (zh) * 2018-07-19 2020-07-17 北京百度网讯科技有限公司 镜像分发方法、装置及存储介质
CN109688232B (zh) * 2019-01-28 2021-09-21 杭州涂鸦信息技术有限公司 一种镜像回溯方法、镜像回溯系统及代理服务器
CN113315795B (zh) * 2020-02-26 2024-03-05 顺丰科技有限公司 云主机镜像的同步方法、装置和存储介质
CN111291017B (zh) * 2020-03-03 2024-04-05 中国工商银行股份有限公司 镜像仓库的镜像存储、提取方法及装置
CN113238831A (zh) * 2021-04-30 2021-08-10 中核武汉核电运行技术股份有限公司 一种基于容器技术的核电生产服务加载方法及装置
CN113505180B (zh) * 2021-09-10 2022-02-22 苏州浪潮智能科技有限公司 一种多云平台中镜像的同步方法、装置、设备及可读介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106528224A (zh) * 2016-11-03 2017-03-22 腾讯科技（深圳）有限公司 一种Docker容器的内容更新方法、服务器及系统
CN106708599A (zh) * 2016-12-01 2017-05-24 携程旅游信息技术（上海）有限公司 虚拟机镜像下发系统及方法
CN106776149A (zh) * 2017-01-04 2017-05-31 郑州云海信息技术有限公司 本地容器镜像上传至镜像仓库的方法及系统
CN107247793A (zh) * 2017-06-21 2017-10-13 平安科技（深圳）有限公司 Docker镜像仓库的镜像同步方法和镜像同步系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105119913A (zh) * 2015-08-13 2015-12-02 东南大学 一种基于Docker的Web服务器架构及各模块之间的交互方法
CN105515864B (zh) * 2015-12-11 2019-05-21 深圳市中润四方信息技术有限公司 容器资源自适应调整方法及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106528224A (zh) * 2016-11-03 2017-03-22 腾讯科技（深圳）有限公司 一种Docker容器的内容更新方法、服务器及系统
CN106708599A (zh) * 2016-12-01 2017-05-24 携程旅游信息技术（上海）有限公司 虚拟机镜像下发系统及方法
CN106776149A (zh) * 2017-01-04 2017-05-31 郑州云海信息技术有限公司 本地容器镜像上传至镜像仓库的方法及系统
CN107247793A (zh) * 2017-06-21 2017-10-13 平安科技（深圳）有限公司 Docker镜像仓库的镜像同步方法和镜像同步系统

Also Published As

Publication number Publication date
CN107247793B (zh) 2020-03-17
CN107247793A (zh) 2017-10-13

Similar Documents

Publication Publication Date Title
WO2018233370A1 (fr) Procédé, système, dispositif et support de stockage lisible par ordinateur de synchronisation d'une image
WO2017088664A1 (fr) Procédé et appareil de traitement de données destinés à un système de fichiers en grappes
WO2019100638A1 (fr) Procédé, dispositif et équipement de synchronisation de données, et support d'informations
WO2019128174A1 (fr) Procédé de lecture audio, téléviseur intelligent, et support d'informations lisible par ordinateur
WO2018107610A1 (fr) Procédé, système et dispositif de traitement de données de service, et support d'informations lisible par ordinateur
WO2018076866A1 (fr) Procédé de traitement de données, dispositif, support de stockage, dispositif électronique, et serveur
WO2018228050A1 (fr) Procédé et dispositif permettant d'empêcher une fuite d'informations sensibles et support de stockage
WO2016000560A1 (fr) Procédé et appareil de transmission de fichier et appareil de réception de fichier
WO2018076811A1 (fr) Dispositif électronique, support d'informations, système, dispositif et procédé de partage de données
WO2018076864A1 (fr) Procédé, appareil, support de stockage et dispositif électronique de synchronisation de données
WO2018014567A1 (fr) Procédé servant à améliorer les performances d'une machine virtuelle, et terminal, dispositif et support de stockage lisible par ordinateur
WO2015106497A1 (fr) Procédé dynamique de mappage équilibré d'interruption en fonction d'un état de programmation de vcpu en cours
WO2018076812A1 (fr) Procédé et dispositif de réponse à une demande de données, support de stockage, serveur et système
WO2019127971A1 (fr) Procédé de synchronisation d'images pour registre d'images, système, dispositif et support d'informations
WO2017206883A1 (fr) Procédé et appareil de traitement d'applications, support de stockage, et dispositif électronique
WO2019056733A1 (fr) Procédé de limitation de volume concurrent, serveur d'application, système, et support de stockage
WO2015120774A1 (fr) Procédé et appareil d'accès à un réseau appliqués à une application mobile
WO2018076875A1 (fr) Procédé de synchronisation de données de sauvegarde, appareil, support de stockage, dispositif électronique, et serveur
WO2017219485A1 (fr) Téléviseur intelligent et procédé de commande de celui-ci
WO2018028121A1 (fr) Procédé et dispositif de gestion de l'espace de stockage d'une partition de données
WO2017206377A1 (fr) Procédé et dispositif de lecture synchrone de programme
WO2018120680A1 (fr) Système de sauvegarde de disque virtuel, procédé, appareil, hôte de service et support d'enregistrement
WO2019161597A1 (fr) Procédé, appareil et dispositif d'envoi d'informations sur la base d'une messagerie instantanée, et support d'informations
WO2016058258A1 (fr) Procédé et système de commande à distance de terminal
WO2023033588A1 (fr) Système de commande de flux de données dans un terminal de virtualisation, et procédé associé

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18821567

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 15/05/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18821567

Country of ref document: EP

Kind code of ref document: A1