summaryrefslogtreecommitdiff
path: root/docs/source/markdown/podman-create.1.md
diff options
context:
space:
mode:
authorDaniel J Walsh <dwalsh@redhat.com>2020-12-09 14:13:53 -0500
committerDaniel J Walsh <dwalsh@redhat.com>2020-12-11 06:07:14 -0500
commit098e0a78856a1cc3b642300dc39f23b93e1f74a8 (patch)
tree087f36309352fb39b890ce6d7ea6b6979ea8f6b4 /docs/source/markdown/podman-create.1.md
parentdd954781e6e308a0bbecfaf6699b41426100a58d (diff)
downloadpodman-098e0a78856a1cc3b642300dc39f23b93e1f74a8.tar.gz
podman-098e0a78856a1cc3b642300dc39f23b93e1f74a8.tar.bz2
podman-098e0a78856a1cc3b642300dc39f23b93e1f74a8.zip
Handle --rm when starting a container
podman start should follow the same behaviour as podman run when removing a container. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Diffstat (limited to 'docs/source/markdown/podman-create.1.md')
-rw-r--r--docs/source/markdown/podman-create.1.md4
1 files changed, 0 insertions, 4 deletions
diff --git a/docs/source/markdown/podman-create.1.md b/docs/source/markdown/podman-create.1.md
index b5f5591a9..8deaa8540 100644
--- a/docs/source/markdown/podman-create.1.md
+++ b/docs/source/markdown/podman-create.1.md
@@ -803,10 +803,6 @@ To generate systemd unit files, please see *podman generate systemd*
Automatically remove the container when it exits. The default is *false*.
-Note that the container will not be removed when it could not be created or
-started successfully. This allows the user to inspect the container after
-failure.
-
#### **--rootfs**
If specified, the first argument refers to an exploded container on the file system.