9b0c8d23bd
Command flags (OPTIONS) in man pages have to date been in haphazard order. Sometimes that order is sensible, e.g., most-important options first, but more often they're just in arbitrary places. This makes life hard for users. Here, I update the man-page-check Makefile script so it checks and enforces alphabetical order in OPTIONS sections. Then -- the hard part -- update all existing man pages to conform to this requirement. Signed-off-by: Ed Santiago <santiago@redhat.com>
1.7 KiB
% podman-network-prune(1)
NAME
podman-network-prune - Remove all unused networks
SYNOPSIS
podman network prune [options]
DESCRIPTION
Remove all unused networks. An unused network is defined by a network which has no containers connected or configured to connect to it. It will not remove the so-called default network which goes by the name of podman.
OPTIONS
--filter
Provide filter values.
The filters argument format is of key=value. If there is more than one filter, then pass multiple OPTIONS: --filter foo=bar --filter bif=baz.
Supported filters:
| Filter | Description |
|---|---|
| label | Only remove networks, with (or without, in the case of label!=[...] is used) the specified labels. |
| until | Only remove networks created before given timestamp. |
The label filter accepts two formats. One is the label=key or label=key=value, which removes networks with the specified labels. The other format is the label!=key or label!=key=value, which removes networks without the specified labels.
The until filter can be Unix timestamps, date formatted timestamps, or Go duration strings (e.g. 10m, 1h30m) computed relative to the machine’s time.
--force, -f
Do not prompt for confirmation
EXAMPLE
Prune networks
podman network prune
SEE ALSO
podman(1), podman-network(1), podman-network-rm(1)
HISTORY
February 2021, Originally compiled by Brent Baude bbaude@redhat.com