diff options
| author | Radostin Stoyanov <rstoyanov1@gmail.com> | 2019-11-02 10:12:38 +0000 |
|---|---|---|
| committer | Radostin Stoyanov <rstoyanov1@gmail.com> | 2019-11-04 00:55:52 +0000 |
| commit | 5293446e0ff39187be4a3f07837e2a145e24c990 (patch) | |
| tree | c0d74466e79fd460ff19acb1d991bf57f6b96990 /cmd/podman/rm.go | |
| parent | 82381072e166f635d9879346ac73c1140709f50f (diff) | |
| download | podman-5293446e0ff39187be4a3f07837e2a145e24c990.tar.gz podman-5293446e0ff39187be4a3f07837e2a145e24c990.tar.bz2 podman-5293446e0ff39187be4a3f07837e2a145e24c990.zip | |
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>
Diffstat (limited to 'cmd/podman/rm.go')
| -rw-r--r-- | cmd/podman/rm.go | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cmd/podman/rm.go b/cmd/podman/rm.go index 89062f524..6329a9d8e 100644 --- a/cmd/podman/rm.go +++ b/cmd/podman/rm.go @@ -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) } |