Docker Usage Note

Now I'll do two things when I create the image:

1. In the build each image, add the specific version number;

2. Write the startup script for all applications.

It is common for an application to create a child process. In the vast majority of systems, you can create a child process, read its output, check the return value on exit, and so on, and then leave it to the INIT process for resource recycling after the program finishes.

But for Docker containers, it's not that simple. In most cases, any child process created will become a zombie process consuming system resources. But if a program that is not properly destroyed by a child process is packaged into a mirror, it can cause a lot of trouble.

Each task corresponding to a container does not mean that a container has only one process

Docker Usage Note