engine: remove mentions of upstart (eol)

Closes #18854

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson 2023-12-06 03:30:01 +01:00
parent 572ced5e4d
commit 53c5af71a9
2 changed files with 3 additions and 4 deletions

View File

@ -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 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 as the main process, and handles reaping of all processes when the
container exits. Handling such processes this way is superior to using a container exits. Handling such processes this way is superior to using a
full-fledged init process such as `sysvinit`, `upstart`, or `systemd` to handle full-fledged init process such as `sysvinit` or `systemd` to handle process
process lifecycle within your container. lifecycle within your container.
If you need to run more than one service within a container, you can achieve If you need to run more than one service within a container, you can achieve
this in a few different ways. this in a few different ways.

View File

@ -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 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 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. [supervisor](http://supervisord.org/) instead.
> **Warning** > **Warning**