mirror of https://github.com/docker/docs.git
engine: remove mentions of upstart (eol)
Closes #18854 Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
parent
572ced5e4d
commit
53c5af71a9
|
@ -25,8 +25,8 @@ your process falls into this category, you can use the `--init` option when you
|
|||
run the container. The `--init` flag inserts a tiny init-process into the
|
||||
container as the main process, and handles reaping of all processes when the
|
||||
container exits. Handling such processes this way is superior to using a
|
||||
full-fledged init process such as `sysvinit`, `upstart`, or `systemd` to handle
|
||||
process lifecycle within your container.
|
||||
full-fledged init process such as `sysvinit` or `systemd` to handle process
|
||||
lifecycle within your container.
|
||||
|
||||
If you need to run more than one service within a container, you can achieve
|
||||
this in a few different ways.
|
||||
|
|
|
@ -72,8 +72,7 @@ Keep the following in mind when using restart policies:
|
|||
|
||||
If restart policies don't suit your needs, such as when processes outside
|
||||
Docker depend on Docker containers, you can use a process manager such as
|
||||
[upstart](http://upstart.ubuntu.com/),
|
||||
[systemd](https://freedesktop.org/wiki/Software/systemd/), or
|
||||
[systemd](https://freedesktop.org/wiki/Software/systemd/) or
|
||||
[supervisor](http://supervisord.org/) instead.
|
||||
|
||||
> **Warning**
|
||||
|
|
Loading…
Reference in New Issue