How to understand data-packed volume container

This article shows you data-packed volume container, the content is concise and easy to understand, can definitely make your eyes bright, through the detailed introduction of this article, I hope you can get something.

In the final analysis, the data of volume container is still in host. Is there a way to put the data completely into volume container and share it with other containers at the same time?

Of course, we usually call this kind of container data-packed volume container. The principle is to package the data into a mirror and then share it through docker managed volume.

We use the following Dockerfile to build the image:

ADD adds static files to the container directory / usr/local/apache2/htdocs.

VOLUME is equivalent to-v and is used to create a docker managed volume,mount point of / usr/local/apache2/htdocs, because this directory is the directory added by ADD, so the existing data is copied to volume.

New build image datapacked:

Because the VOLUME directive is already used in Dockerfile, you don't need to specify the mount point of volume here. Start the httpd container and use data-packed volume container

The container can read the data in volume correctly. Data-packed volume container is self-contained, does not rely on host to provide data, has a strong portability, and is very suitable for scenarios that only use static data, such as application configuration information, web server static files, and so on.

The above content is data-packed volume container. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.