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

Today, I will talk to you about the relationship between docker and CCS, which may not be well understood by many people. In order to make you understand better, the editor has summarized the following for you. I hope you can get something from this article.

The usability management of containerized microservice applications is complex because there are many items to be measured and tracked. Moreover, measuring system availability requires a well-defined state model. Object states need to be manageable, associative, and propagable across physical facilities and software entities.

Using an appropriate system management platform, it is possible to measure, track, and report on the availability of services, applications, or environments. By focusing on service availability, operators can easily achieve "signal-to-noise separation" and only focus on the issues that affect the service.

For the availability of container services, we need to know a few things about building and using docker containers.

1. Don't rely too much on the IP address inside the container

Each container has an internal IP. The IP is not fixed. The IP changes when we start the docker container or stop the container. If we want applications or microservice modules to communicate between containers, the right thing to do is to pass the host name and port number by setting environment variables.

two。 When building a container image, don't build only one layer.

As we all know, the file system of Docker is layered, so when creating an image, we should build a separate layer of the operating system as the basic image, and then create a separate layer of the user name definition file, the runtime installation environment, and the configuration file, and finally the application image layer. By doing so, it will be much easier for us to rebuild, manage, and publish images in the future.

3. Don't just type "latest" when you tag the image.

Latest is actually the equivalent of a snapshot in Maven. Because the container's file system is hierarchical, we'd better type a few more tag to the image.

If there is only latest, we may find that the application won't work when we run it again after a while, because the parent layer of the application (that is, the layer in Dockerfile that follows the FROM command) is overwritten by the newer version, and the new version is not backward compatible.

It is also possible that when you took the image from build cache, you got the wrong "latest" image. Avoid using latest when deploying containers in a production environment, otherwise it can easily lead to the problem of not being able to track and record the image version.

After reading the above, do you have any further understanding of the relationship between docker and container services? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

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.