Browse Prior Art Database

System and Method to conserve images incrementally and adaptively in Docker

IP.com Disclosure Number: IPCOM000245276D
Publication Date: 2016-Feb-25
Document File: 7 page(s) / 109K

Publishing Venue

The IP.com Prior Art Database

Abstract

In Docker, to allow write operation under the premise of OS image unchanged,Docker fetches in AUFS technology: the modification for the read-only layer file or directory will only exist in the upper writeable layer. But, it will lead to too much dependences between layers which will affect the efficiency. To adaptively adjust the dependences of images to improve the efficiency, when modify a file, hold the midifications on memory and merge the file into the layer which is the child of that in which has the same file and record the logical location of the file; When commit a image, merge parent with every child and generate some new nodes, record the logical and physical locations.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 66% of the total text.

Page 01 of 7

System and Method to conserve images incrementally and adaptively in Docker


1) If we are careless with the images, what will happen?
---Too much dependences will be generated, not only it will affect the efficiency to load the images, but also it will have an impact on AUFS file system.

2) If we merge some image files together mandatory, what will happen?

---Dependences relationships will be disrupted, some images will disappear which may be useful in the future.

Core idea of our disclosure: a) a new component for images management in Docker servers; b) a new method to adjust hierarchy dependence adaptively between images.

A new component is introduced in the Docker framework which will locate on each Docker server

--File monitor module: distinguish between logical files and physical files, 1)monitor the references of the files. When modify a file, modification will be hold on memory and the component will check other references of it . Merge the file into the layer which is the child of that in which has the same file and record the logical location of the file .


2)Image monitor module: distinguish between logical layers and physical layers, be responsible for the transformation of the logic layer and physical layer. When commit a image, if the number of references is over a threshold, send request to merge module to make the child image as a brother image;


3)Merge module: merge files and their modifications; merge images and adjust their hierarchy dependence --...