docker load: Import Images from a Tar Archive

Restore images (with tags and layers) from a docker save tar.

docker load reads a tar archive created by docker save and restores the images, layers, and tags into the local store. This page covers loading from a file or stdin.

What it does

docker load is the inverse of docker save. It imports a full image (layers + metadata + tags). Contrast docker import, which creates a single-layer image from a flat filesystem tar with no history.

Common usage

Terminal

docker load -i myapp.tar
gunzip -c myapp.tar.gz | docker load
docker load < images.tar

Common errors in CI

"open /path/to.tar: no such file or directory" means the cache-restore step did not produce the file - verify the cache key hit before docker load. "invalid tar header" or "unexpected EOF" indicates a corrupted or truncated archive (interrupted save or partial cache); regenerate it. Loading does not run anything; it only populates the image store.

Related guides

docker save: Export Images to a Tar ArchiveHow docker save works: serializing one or more images to a tar archive with layers and metadata, for caching… docker import: Create an Image from a TarballHow docker import works: building a single-layer image from a filesystem tar, setting CMD on import, and the… docker images: List Images, Filters & FormattingHow docker images works: listing local images, filtering dangling layers, custom formatting, and using it to… docker run: Usage, Options & Common CI ErrorsHow docker run works: starting a container from an image, port and volume mapping, env vars, --rm cleanup, an…