Skip to content

Fix typos in the Start containers automatically manual #22555

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −4
Open

Fix typos in the Start containers automatically manual #22555

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions content/manuals/engine/containers/start-containers-automatically.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,14 +10,14 @@ aliases:
- /config/containers/start-containers-automatically/
---

Docker provides [restart policies](/manuals/engine/containers/run.md#restart-policies---restart)
Docker provides [restart policies](/manuals/engine/containers/start-containers-automatically.md#use-a-restart-policy)
to control whether your containers start automatically when they exit, or when
Docker restarts. Restart policies start linked containers in the correct order.
Docker recommends that you use restart policies, and avoid using process
managers to start containers.

Restart policies are different from the `--live-restore` flag of the `dockerd`
command. Using `--live-restore` lets you to keep your containers running during
command. Using `--live-restore` lets you keep your containers running during
a Docker upgrade, though networking and user input are interrupted.

## Use a restart policy
Expand Down Expand Up @@ -115,7 +115,7 @@ container. This behavior is illustrated in the following example.
$
```

4. Running `docker ps` shows that is still running or restarting, thanks to the
4. Running `docker ps` shows that it is still running or restarting, thanks to the
restart policy. The CLI session has already exited, however. It doesn't
survive the initial container exit.

Expand Down Expand Up @@ -157,7 +157,7 @@ process manager for more details.
### Using a process manager inside containers

Process managers can also run within the container to check whether a process is
running and starts/restart it if not.
running and start/restart it if it's not.

> [!WARNING]
>
Expand Down