Skip to content

Update run.md #2806

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

Closed
Crowbrammer wants to merge 1 commit into from
+6 −6
Closed

Update run.md #2806

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
12 changes: 6 additions & 6 deletions docs/reference/run.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -650,13 +650,13 @@ $ docker run busybox /bin/sh -c 'exit 3'; echo $?

## Clean up (--rm)

By default a container's file system persists even after the container
exits. This makes debugging a lot easier (since you can inspect the
final state) and you retain all your data by default. But if you are
By default a container's file system persists after the container
exits. This makes debugging easier (since you can inspect the
final state), and you retain your data by default. But if you're
running short-term **foreground** processes, these container file
systems can really pile up. If instead you'd like Docker to
**automatically clean up the container and remove the file system when
the container exits**, you can add the `--rm` flag:
systems can pile up. Docker can **automatically clean up the
container and remove the file system when the container exits**,
if you add the `--rm` flag:

--rm=false: Automatically remove the container when it exits

Expand Down