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.
"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.
Frequently asked questions
docker load: Import Images from a Tar Archive?
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 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.