Files
podman/docs/source/markdown/podman-volume-import.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

1.1 KiB

% podman-volume-import 1

NAME

podman-volume-import - Import tarball contents into an existing podman volume

SYNOPSIS

podman volume import volume [source]

DESCRIPTION

podman volume import imports the contents of a tarball into the podman volume's mount point. The contents of the volume is merged with the content of the tarball with the latter taking precedence. podman volume import can consume piped input when using - as source path.

The given volume must already exist and is not created by podman volume import.

--help

Print usage statement

EXAMPLES

Import named volume content from the specified file.

$ podman volume import myvol test.tar

Import named volume content from stdin.

$ gunzip -c hello.tar.gz | podman volume import myvol -

Export the content from named volume and pipe it into the named volume via stdin.

$ podman volume export oldmyvol | podman volume import myvol -

SEE ALSO

podman(1), podman-volume(1), podman-volume-export(1)