Add podman rm --volumes flag

While this is not implemented yet, it is needed for working with existing
docker scripts.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>

Closes: #1460
Approved by: mheon
This commit is contained in:
Daniel J Walsh
2018-09-13 08:36:49 -04:00
committed by Atomic Bot
parent facab2aec5
commit 61eda671ec
3 changed files with 15 additions and 4 deletions

View File

@ -12,15 +12,19 @@ import (
var ( var (
rmFlags = []cli.Flag{ rmFlags = []cli.Flag{
cli.BoolFlag{
Name: "force, f",
Usage: "Force removal of a running container. The default is false",
},
cli.BoolFlag{ cli.BoolFlag{
Name: "all, a", Name: "all, a",
Usage: "Remove all containers", Usage: "Remove all containers",
}, },
cli.BoolFlag{
Name: "force, f",
Usage: "Force removal of a running container. The default is false",
},
LatestFlag, LatestFlag,
cli.BoolFlag{
Name: "volumes, v",
Usage: "Remove the volumes associated with the container (Not implemented yet)",
},
} }
rmDescription = fmt.Sprintf(` rmDescription = fmt.Sprintf(`
Podman rm will remove one or more containers from the host. Podman rm will remove one or more containers from the host.

View File

@ -1744,6 +1744,8 @@ _podman_rm() {
-f -f
--latest --latest
-l -l
--volumes
-v
" "
local options_with_args=" local options_with_args="

View File

@ -23,6 +23,11 @@ Remove all containers. Can be used in conjunction with -f as well.
Instead of providing the container name or ID, use the last created container. If you use methods other than Podman Instead of providing the container name or ID, use the last created container. If you use methods other than Podman
to run containers such as CRI-O, the last started container could be from either of those methods. to run containers such as CRI-O, the last started container could be from either of those methods.
**--volumes, -v**
Remove the volumes associated with the container. (Not yet implemented)
## EXAMPLE ## EXAMPLE
podman rm mywebserver podman rm mywebserver