Files
podman/docs/source/markdown/podman-volume-export.1.md
Matt Heon 98876454cb Refactor volume import to support the remote client
As with `volume export`, this was coded up exclusively in cmd/
instead of in libpod. Move it into Libpod, add a REST endpoint,
add bindings, and now everything talks using the ContainerEngine
wiring.

Also similar to `volume export` this also makes things work much
better with volumes that require mounting - we can now guarantee
they're actually mounted, instead of just hoping.

Includes some refactoring of `volume export` as well, to simplify
its implementation and ensure both Import and Export work with
readers/writers, as opposed to just files.

Fixes #26409

Signed-off-by: Matt Heon <mheon@redhat.com>
2025-06-23 13:42:22 -04:00

37 lines
823 B
Markdown

% podman-volume-export 1
## NAME
podman\-volume\-export - Export 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.
**podman volume export [OPTIONS] VOLUME**
## OPTIONS
#### **--help**
Print usage statement
#### **--output**, **-o**=*file*
Write to a file, default is STDOUT
## EXAMPLES
Export named volume content into the specified file.
```
$ 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)**