Hauler Store Load
Overview​
hauler store load unpacks a haul archive back into a content store.
This is the first step on the airgapped side of the workflow: once the archive produced by hauler store save has been transported to the disconnected environment, load restores it into a usable content store. From there you can inspect it with hauler store info, serve it with hauler store serve, or push it into an existing registry with hauler store copy. Multiple archives can be loaded into the same store, and chunked archives are rejoined automatically.
As of v1.3, Hauler also supports loading content from a Docker-saved tarball.
Note: Podman-saved tarballs are not currently supported.
An example with available flags...
hauler store load --filename <haul-name>
Command Overview​
Usage:
hauler store load [flags]
Flags:
-f, --filename strings (Optional) Specify the name of inputted haul(s) (default [haul.tar.zst])
-h, --help help for load
Global Flags:
-d, --haulerdir string Set the location of the hauler directory (default $HOME/.hauler)
--ignore-errors Ignore/Bypass errors (i.e. warn on error) (defaults false)
-l, --log-level string Set the logging level (i.e. info, debug, warn) (default "info")
-r, --retries int Set the number of retries for operations (default 3)
-s, --store string Set the directory to use for the content store
-t, --tempdir string (Optional) Override the default temporary directory determined by the OS
Example Commands for Load​
# load the default haul (haul.tar.zst)
hauler store load
# load a specific haul
hauler store load --filename my-haul.tar.zst
# load multiple hauls into the same store
hauler store load --filename one.tar.zst --filename two.tar.zst
# load a remote haul
hauler store load --filename https://example.com/haul.tar.zst
Loading a Chunked Haul​
If the archive was split with hauler store save --chunk-size, pass the base filename and Hauler automatically rejoins the chunks (matched by the <base>_*<ext> pattern) before loading:
hauler store load --filename haul.tar.zst