Container management frameworks, such as Docker, pack applications and their complex software environment in self-contained images, which facilitates application deployment, distribution, and sharing. Currently, container images are organized in a multi-layer file-system manner. For example, Docker uses AUFS to organize its container image storage. However, when a new version is created, all the changes are stored in a new layer via a Copy-On-Write mechanism, which can trigger a heavy burden for the network and storage. There are also other image storage approaches such as chunk-based technology. In this paper, we suggest that the container image storage system should not use one storage technology for all images, but should choose different technology for concrete images according to the image's distinct features. We design some experiments to compare the layer-based and chuck-based technology. And based on the analysis of the collected data, this paper gives some principles for the selection of image management techniques and discusses some interesting potential research topics.
[1]
Andrea C. Arpaci-Dusseau,et al.
Slacker: Fast Distribution with Lazy Docker Containers
,
2016,
FAST.
[2]
Dirk Merkel,et al.
Docker: lightweight Linux containers for consistent development and deployment
,
2014
.
[3]
Douglas Thain,et al.
Wharf: Sharing Docker Images in a Distributed File System
,
2018,
SoCC.
[4]
Zibin Zheng,et al.
Collaboration environment for JointCloud computing
,
2017
.
[5]
Bo An,et al.
Providing Virtual Cloud for Special Purposes on Demand in JointCloud Computing Environment
,
2017,
Journal of Computer Science and Technology.
[6]
Mohamed Mohamed,et al.
Improving Docker Registry Design Based on Production Workload Analysis
,
2018,
FAST.