aboutsummaryrefslogtreecommitdiff
path: root/cmd/podman/cliconfig
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2019-09-09 15:37:35 -0500
committerbaude <bbaude@redhat.com>2019-09-12 14:03:52 -0500
commitb94ea07265045f447572c264ef62e7960f484b58 (patch)
tree10ed1b8a28515fb083d4c306055e1db9da3c1f81 /cmd/podman/cliconfig
parentaf8fedcc78674d71d43ca3000438c42b7b6b6994 (diff)
downloadpodman-b94ea07265045f447572c264ef62e7960f484b58.tar.gz
podman-b94ea07265045f447572c264ef62e7960f484b58.tar.bz2
podman-b94ea07265045f447572c264ef62e7960f484b58.zip
enhance podman network rm
when removing a podman network, we need to make sure we delete the network interface if one was ever created (by running a container). also, when removing networks, we check if any containers are using the network. if they are, we error out unless the user provides a 'force' option which will remove the containers in question. Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'cmd/podman/cliconfig')
-rw-r--r--cmd/podman/cliconfig/config.go1
1 files changed, 1 insertions, 0 deletions
diff --git a/cmd/podman/cliconfig/config.go b/cmd/podman/cliconfig/config.go
index bf88e853b..e0ce202cc 100644
--- a/cmd/podman/cliconfig/config.go
+++ b/cmd/podman/cliconfig/config.go
@@ -280,6 +280,7 @@ type NetworkListValues struct {
type NetworkRmValues struct {
PodmanCommand
+ Force bool
}
type NetworkInspectValues struct {