Shulou(Shulou.com)06/01 Report--

This article shows you how to use docker after creating a container, the content is concise and easy to understand, it will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

How to use docker after creating a container? Docker container technology can solve many problems faced by enterprise IT business at present, and it has many advantages. After creating a container with docker, you should avoid the following misunderstandings when using it.

Do not store data in a container

Containers can be stopped, destroyed or migrated at any time. For example, if the version of the application running in a container is 1.0, we can upgrade the application to 1.1 in minutes without any impact on the data. Therefore, if the user wants to store data, it is best to use data volumes to store it.

However, when using volume storage data, it should be noted that if two containers share a data volume and write data into it, it is possible to cause the program to crash. We should take this into account when designing our application, and to be foolproof, the application should have a specific mechanism to ensure that there are no errors when writing data to the shared data store.

Do not store the authentication password in the image

It is better to use environment variables. If we put the user name / password value pair in the image, we have to deal with it one by one by hard coding, which is estimated to be a hassle that no one wants to do. Therefore, it is best to use the side of the environment variable to obtain this kind of information from outside the container.

Do not deliver the application in blocks

In the eyes of some users, container service is no different from a virtual machine, so some people tend to deploy applications to several containers that are currently running. This approach is not much of a problem during the development phase, because deployment and debugging are done frequently during development.

But when it comes to continuous delivery, the next step is QA testing and formal production, which is not appropriate. At this stage, we should take full account of the immutable nature of the container, preferably by packaging the application into an image for delivery.

Do not turn the locally running container into an image

In other words, do not use the "docker commit" command when creating a mirror. It is totally undesirable to build an image in this way, because it cannot be repeated.

When we create an image, we should create it from Dockerfile, or use other S2I (build image from source file), so that the image can be regenerated, and if we store the image in a system that provides version control, such as git, we can also track changes to Dockerfile.

The above is how to use docker after creating a 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.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.