79

How do we take container snapshots and load the snapshot in another docker host . I like to know the container snapshoting and not for image. I get confused with export/import and save/load commands in docker. I like to get more clarity or doc to understand them more deeply .

The snapshot to have the metadata to run the container and the roofs . The exact state to be there in the other docker host. Help in this direction would be great.

tanmally
  • 996
  • 1
  • 9
  • 13

2 Answers2

71

The command docker commit takes a snapshot of your container. That snapshot is an image, which you can put on a (private) repository to be able to pull it on another host.

An option that does not use an image (which you say you want to avoid) is indeed save and load. According to the documentation this saves your container with all file layers. So if you have a setup with child containers such as Ubuntu > JavaJDK > Elasticsearch > my-container, all 4 file layers would get in there. But you may have the first 3 layers already present as images on the other host, in which case save amounts to a lot of overhead. Then, you can use export and import, which according to the documentation only exports the top file layer (in other words, the container, and not the images below it).

More information on the images, container, file layers etc can be found in the official documentation (e.g. file system.

Ondra Žižka
  • 43,948
  • 41
  • 217
  • 277
qkrijger
  • 26,686
  • 6
  • 36
  • 37
  • If I use export and then import the problem is I cant create a container that can be run with the imported data right ? Can I create a container using import if so can I run it ? – tanmally Mar 13 '14 at 13:49
  • 1
    The full docs for docker are at https://docs.docker.com/ @qkrijger glossory link is to file systems layers – pn1 dude Jun 16 '14 at 15:11
20

If you're looking for an "exact state", including the execution state, you may need to use CRIU (checkpoint).

Given a linux host machine, Docker can use CRIU to save the execution state of the container. CRIU is still "experimental", and you can see all the possible commands (after enabling experimental mode) by running:

docker checkpoint

You can use the --save-dir option to put the checkpoint in the directory of your choosing.

You can then use

docker start --checkpoint (checkpoint name) --checkpoint-dir (checkpoint directory)

to restore the checkpoint.

If moving servers, you may need to bring the image along with you.

You can read more on the docs: https://docs.docker.com/engine/reference/commandline/checkpoint/

dGRAMOP
  • 753
  • 5
  • 19