After docker run, the status is always Exited

add -it

docker run -it -name test -d nginx:latest /bin/bash

-d: Run the container in the background and return the container ID;

-i: Run the container in interactive mode, usually used with -t;

-t: reallocate a pseudo input terminal for the container, usually used together with -i;

Additional knowledge: docker-compose starts nginx through sh command and the container automatically exits with code 0

In the template file used by docker-compose, the container is started automatically by executing the sh command through the entrypoint or command parameter to start the nginx service, but the container automatically exits after docker-compose up

nginx-web1 exited with code 0

nginx-web2 exited with code 0

nginx-web3 exited with code 0

Reason: Docker's mechanism is to run the container in the background. There must be at least one foreground process. If the command run by the container is not a command that has been suspended (such as running top, tail), it will automatically exit.

Solution: You can use the sh command containing the -g "daemon off;" configuration item to start the nginx service in the foreground mode.

nginx -c /usr/local/nginx/conf/nginx.conf -g "daemon off;"

If the container needs to start multiple processes at the same time, just suspend one of them to the foreground, for example:

service php-fpm start && nginx -g "daemon off;"

or

service php-fpm start && service nginx start && tail -f /var/log/nginx/error.log

The above article "The status is always Exited after docker run" is all the content that the editor shared with you. I hope it can give you a reference. I also hope that you will support 123WORDPRESS.COM.