mirror of
https://github.com/containers/podman.git
synced 2025-07-30 20:02:37 +08:00
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>
38 lines
832 B
Markdown
38 lines
832 B
Markdown
% podman-volume-export(1)
|
|
|
|
## NAME
|
|
podman\-volume\-export - Exports volume to external tar
|
|
|
|
## SYNOPSIS
|
|
**podman volume export** [*options*] *volume*
|
|
|
|
## DESCRIPTION
|
|
|
|
**podman volume export** exports the contents of a podman volume and saves it as a tarball
|
|
on the local machine. **podman volume export** writes to STDOUT by default and can be
|
|
redirected to a file using the `--output` flag.
|
|
|
|
Note: Following command is not supported by podman-remote.
|
|
|
|
**podman volume export [OPTIONS] VOLUME**
|
|
|
|
## OPTIONS
|
|
|
|
#### **--help**
|
|
|
|
Print usage statement
|
|
|
|
#### **--output**, **-o**=*file*
|
|
|
|
Write to a file, default is STDOUT
|
|
|
|
## EXAMPLES
|
|
|
|
```
|
|
$ podman volume export myvol --output myvol.tar
|
|
|
|
```
|
|
|
|
## SEE ALSO
|
|
**[podman(1)](podman.1.md)**, **[podman-volume(1)](podman-volume.1.md)**, **[podman-volume-import(1)](podman-volume-import.1.md)**
|