You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 <[email protected]>
@@ -27,7 +29,7 @@ Allow content of volume to be exported into external tar.`
27
29
)
28
30
29
31
var (
30
-
cliExportOpts entities.VolumeExportOptions
32
+
targetPathstring
31
33
)
32
34
33
35
funcinit() {
@@ -38,20 +40,30 @@ func init() {
38
40
flags:=exportCommand.Flags()
39
41
40
42
outputFlagName:="output"
41
-
flags.StringVarP(&cliExportOpts.OutputPath, outputFlagName, "o", "/dev/stdout", "Write to a specified file (default: stdout, which must be redirected)")
43
+
flags.StringVarP(&targetPath, outputFlagName, "o", "", "Write to a specified file (default: stdout, which must be redirected)")
0 commit comments