Remove process manager section.

See: https://docs.docker.com/config/containers/start-containers-automatically/#use-a-process-manager

> To use a process manager, configure it to start your container or service using the same docker start or docker service command you would normally use to start the container manually.
This commit is contained in:
Weizhe Sun 2019-01-23 07:32:11 +00:00
parent d38b8f44b1
commit 510429a0b6

View file

@ -105,8 +105,6 @@ Another useful option is `docker run --name yourname docker_image` because when
* [`docker kill`](https://docs.docker.com/engine/reference/commandline/kill) sends a SIGKILL to a running container.
* [`docker attach`](https://docs.docker.com/engine/reference/commandline/attach) will connect to a running container.
If you want to integrate a container with a [host process manager](https://docs.docker.com/engine/admin/host_integration/), start the daemon with `-r=false` then use `docker start -a`.
If you want to expose container ports through the host, see the [exposing ports](#exposing-ports) section.
Restart policies on crashed docker instances are [covered here](http://container42.com/2014/09/30/docker-restart-policies/).