docs: Update "podman container rm -v" description

In commit 52df1fa (Fix volume handling in podman) was implemented the
--volume option for podman remove. However, its behaviour changed after
83db80c (Only remove image volumes when removing containers).

This commit updates the description of this option to reflect the new
behaviour.

Signed-off-by: Radostin Stoyanov <rstoyanov1@gmail.com>
This commit is contained in:
Radostin Stoyanov
2019-11-02 10:12:38 +00:00
parent 82381072e1
commit 5293446e0f
2 changed files with 3 additions and 2 deletions

View File

@ -43,7 +43,7 @@ func init() {
flags.BoolVarP(&rmCommand.Force, "force", "f", false, "Force removal of a running or unusable container. The default is false")
flags.BoolVarP(&rmCommand.Latest, "latest", "l", false, "Act on the latest container podman is aware of")
flags.BoolVar(&rmCommand.Storage, "storage", false, "Remove container from storage library")
flags.BoolVarP(&rmCommand.Volumes, "volumes", "v", false, "Remove the volumes associated with the container")
flags.BoolVarP(&rmCommand.Volumes, "volumes", "v", false, "Remove anonymous volumes associated with the container")
markFlagHiddenForRemoteClient("storage", flags)
markFlagHiddenForRemoteClient("latest", flags)
}

View File

@ -42,7 +42,8 @@ The storage option conflicts with the **--all**, **--latest**, and **--volumes**
**--volumes**, **-v**
Remove the volumes associated with the container.
Remove anonymous volumes associated with the container. This does not include named volumes
created with `podman volume create`, or the `--volume` option of `podman run` and `podman create`.
## EXAMPLE
Remove a container by its name *mywebserver*