From 098e0a78856a1cc3b642300dc39f23b93e1f74a8 Mon Sep 17 00:00:00 2001 From: Daniel J Walsh Date: Wed, 9 Dec 2020 14:13:53 -0500 Subject: 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 --- docs/source/markdown/podman-create.1.md | 4 ---- 1 file changed, 4 deletions(-) (limited to 'docs/source/markdown/podman-create.1.md') 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. -- cgit v1.2.3-54-g00ecf