Analysis of Docker's method for creating local images

The so-called container actually creates a readable and writable file hierarchy based on the parent image. All modification operations are performed on this file hierarchy, and the parent image is not affected. If the reader needs to create a new local image based on this modification, there are two different ways. This article first looks at the first way: commit.

Create a container

First, run a container based on the local image as follows:

Command Explanation:

• First, execute the docker images command to view the local image.
• Create a container named nginx based on the nginx image in the local image and start it.
• Copy a file named index.html from the host to the container.
• Access the container and find that the changes have taken effect.
• Next, create a new container named nginx2.
• When accessing nginx2, I found that the default page in nginx2 was still the default page of nginx and had not changed.

Create a local image

Next, create a local image based on the first container just created, as follows:

Command Explanation:

• The parameter -m is a brief description of the created image.
• --author indicates the author of the image.
• ce1fe32739402 indicates the ID of the container on which the image is created.
• sang/nginx indicates the warehouse name, sang is the namespace, and nginx is the image name.
• v1 indicates the tag of the repository.
• After the creation is complete, you can view the image you just created through the docker images command.
• Run a container through the image you just created and access the container. You will find that the default homepage of nginx has changed.

The above is the full content of this article. I hope it will be helpful for everyone’s study. I also hope that everyone will support 123WORDPRESS.COM.