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

This article mainly introduces "how to use the docker container". In the daily operation, I believe many people have doubts about how to use the docker container. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about how to use the docker container. Next, please follow the editor to study!

Do not release two copies of the application

Some people think of containers as virtual machines. Most of them tend to think that they should publish their applications in existing running containers. This is true during the development phase, when you need to constantly deploy and debug; but for a continuously deployed pipeline in quality assurance and production, your application should be part of the mirror. Remember: the container should remain the same.

Do not use single-layer mirroring

To make more rational use of hierarchical file systems, always create your own basic mirror layer for your operating system, another layer for security and user definition, one layer for library installation, one layer for configuration, and the last layer for applications. This will be easy to rebuild and manage an image, as well as easy to distribute.

Don't rely on IP addresses

Each container service has its own internal IP address, which may change if you start and stop it. If your application or microservice needs to communicate with other containers, use any naming and / or environment variables to pass the appropriate information from one container to another.

Don't just use the "latest" label

The latest tags are like "snapshots" of Maven users. Tags are encouraged, especially if you have a hierarchical file system. You don't want to be surprised to find that the application doesn't work when you create a mirror 2 months later, because the top tier is replaced by a new version that is not backward compatible, or there is an incorrect "latest" version in the creation cache. Avoid using the latest when deploying containers in production.

Do not store credentials in the mirror

Use environment variables and do not write down any username / password in the image. Use environment variables to get this information from outside the container. A good example is the postgres image.

At this point, the study on "how to use the docker container" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.