Files
podman/docs/source/markdown/podman-network-rm.1.md
Daniel J Walsh 22474095ab Fix handling of remove of bogus volumes, networks and Pods
In podman containers rm and podman images rm, the commands
exit with error code 1 if the object does not exists.

This PR implements similar functionality to volumes, networks, and Pods.

Similarly if volumes or Networks are in use by other containers, and return
exit code 2.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2020-09-29 15:52:43 -04:00

48 lines
1004 B
Markdown

% podman-network-rm(1)
## NAME
podman\-network\-rm - Remove one or more CNI networks
## SYNOPSIS
**podman network rm** [*options*] [*network...*]
## DESCRIPTION
Delete one or more Podman networks.
## OPTIONS
**--force**, **-f**
The `force` option will remove all containers that use the named network. If the container is
running, the container will be stopped and removed.
## EXAMPLE
Delete the `cni-podman9` network
```
# podman network rm cni-podman9
Deleted: cni-podman9
```
Delete the `fred` network and all containers associated with the network.
```
# podman network rm -f fred
Deleted: fred
```
## Exit Status
**0** All specified networks removed
**1** One of the specified networks did not exist, and no other failures
**2** The network is in use by a container or a Pod
**125** The command fails for any other reason
## SEE ALSO
podman(1), podman-network(1), podman-network-inspect(1)
## HISTORY
August 2019, Originally compiled by Brent Baude <bbaude@redhat.com>