diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2020-03-04 10:58:10 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-04 10:58:10 -0500 |
| commit | 90eef95cb1591f20f5716225cf9b2c8c415fc3fc (patch) | |
| tree | 9f19d9affffb9c57b5888e2fb3d12b9c642d4a73 /docs/source/markdown | |
| parent | a8bc423e2989ceff1ee2ca79d6c1bd8314901e11 (diff) | |
| parent | 11e5c53d1191f7a324f212aa2ca2ec2aad1b4676 (diff) | |
| download | podman-90eef95cb1591f20f5716225cf9b2c8c415fc3fc.tar.gz podman-90eef95cb1591f20f5716225cf9b2c8c415fc3fc.tar.bz2 podman-90eef95cb1591f20f5716225cf9b2c8c415fc3fc.zip | |
Merge pull request #4772 from boaz0/closes_4628
Add the rmi flag to podman-run to delete container image
Diffstat (limited to 'docs/source/markdown')
| -rw-r--r-- | docs/source/markdown/podman-container-cleanup.1.md | 8 | ||||
| -rw-r--r-- | docs/source/markdown/podman-run.1.md | 5 |
2 files changed, 13 insertions, 0 deletions
diff --git a/docs/source/markdown/podman-container-cleanup.1.md b/docs/source/markdown/podman-container-cleanup.1.md index 69e21ce9f..86e6b4316 100644 --- a/docs/source/markdown/podman-container-cleanup.1.md +++ b/docs/source/markdown/podman-container-cleanup.1.md @@ -22,6 +22,14 @@ to run containers such as CRI-O, the last started container could be from either The latest option is not supported on the remote client. +**--rm** + +After cleanup, remove the container entirely. + +**--rmi** + +After cleanup, remove the image entirely. + ## EXAMPLE `podman container cleanup mywebserver` diff --git a/docs/source/markdown/podman-run.1.md b/docs/source/markdown/podman-run.1.md index 220b32a46..bc99a83ca 100644 --- a/docs/source/markdown/podman-run.1.md +++ b/docs/source/markdown/podman-run.1.md @@ -689,6 +689,11 @@ 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. +**--rmi**=*true|false* + +After exit of the container, remove the image unless another +container is using it. The default is *false*. + **--rootfs** If specified, the first argument refers to an exploded container on the file system. |