{"id":5463,"date":"2018-10-10T05:56:04","date_gmt":"2018-10-10T05:56:04","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=5463"},"modified":"2022-10-03T14:25:56","modified_gmt":"2022-10-03T14:25:56","slug":"difference-between-docker-load-and-docker-import","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/difference-between-docker-load-and-docker-import\/","title":{"rendered":"Docker Tutorials: Difference between Docker Load and Docker Import"},"content":{"rendered":"

\"\"<\/p>\n

If you want to “flatten” an image and avoid the history which has multiple layers, docker export and import is the best way to do that.<\/p>\n

docker save<\/strong> – docker save will indeed produce a tarball, but with all parent layers, and all tags + versions.<\/p>\n

docker export –<\/strong> docker export does also produce a tarball, but without any layer\/history.<\/p>\n

However, once those tarballs are produced, load\/import are there to:<\/p>\n

docker import –<\/strong> docker import creates one image from one tarball which is not even an image (just a filesystem you want to import as an image). Create an empty filesystem image and import the contents of the tarball<\/p>\n

docker load –<\/strong> docker load creates potentially multiple images from a tarred repository (since docker save can save multiple images in a tarball). Loads a tarred repository from a file or the standard input stream<\/p>\n

 <\/p>\n

[CODE]$ docker run -it ubuntu
\n$ cd \/opt\/
\nroot@20a8011f2e65:\/opt# touch DevOpsSchool.com
\nroot@20a8011f2e65:\/opt# ls
\nDevOpsSchool.com<\/p>\n

CNTRL + P + Q<\/p>\n

$ docker ps
\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
\n20a8011f2e65 ubuntu “\/bin\/bash” 24 seconds ago Up 23 seconds thirsty_wilson<\/p>\n

$ docker export -o ubuntu-devops.tar 20a8011f2e65
\n$ docker help import
\nUsage: docker import [OPTIONS] file|URL|- [REPOSITORY[:TAG]]
\nImport the contents from a tarball to create a filesystem image<\/p>\n

Options:
\n-c, –change list Apply Dockerfile instruction to the created image
\n–help Print usage
\n-m, –message string Set commit message for imported image<\/p>\n

$ docker import -m”ubuntu+devopsschool” ubuntu-devops. tar
\nsha256:c9b6e68b24325d86c511cd45071e69cacd185835b427c83f1cecf7e2e001b13e<\/p>\n

$ docker images
\nREPOSITORY TAG IMAGE ID CREATED SIZE
\nc9b6e68b2432 4 seconds ago 69.8MB<\/p>\n

$ docker tag c9b6e68b2432 ubuntu-devopsschool.com
\n$ docker images
\nREPOSITORY TAG IMAGE ID CREATED SIZE
\nubuntu-devopsschool.com latest c9b6e68b2432 25 seconds ago 69.8MB<\/p>\n

$ docker run -itd ubuntu-devopsschool.com ls \/opt
\n04ed9676981d943f85de58b9885f0347f4ed11c96d97546d484173b7fcd48101<\/p>\n

$ docker ps
\nCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
\n20a8011f2e65 ubuntu “\/bin\/bash” 2 minutes ago Up 2 minutes<\/p>\n

$ docker exec 20a8011f2e65 ls \/opt
\nDevOpsSchool.com<\/p>\n

$ docker history ubuntu-devopsschool.com
\nIMAGE CREATED CREATED BY SIZE COMMENT
\nc9b6e68b2432 About a minute ago 69.8MB ubuntu+devopsschool[\/CODE]<\/p>\n

Docker Tutorials Fundamental To Advanced-2021 Crash Course:- https:\/\/bit.ly\/3hOIbTB<\/a><\/p>\n\n