Changes

32 bytes added ,  18:10, 18 July 2016
m
Line 13: Line 13:  
     docker-1.10.0-dev daemon -D --graph=/var/lib/docker-dev --host unix:///var/run/docker-dev.sock
 
     docker-1.10.0-dev daemon -D --graph=/var/lib/docker-dev --host unix:///var/run/docker-dev.sock
   −
The *graph* and *host* options will prevent colliding with an existing installation of Docker, but you can replace your existing docker if desired. In another shell, you can then connect to that daemon:
+
The '''graph''' and '''host''' options will prevent colliding with an existing installation of Docker, but you can replace your existing docker if desired. In another shell, you can then connect to that daemon:
    
     docker-1.10.0-dev --host unix:///var/run/docker-dev.sock run -d busybox top
 
     docker-1.10.0-dev --host unix:///var/run/docker-dev.sock run -d busybox top
Line 19: Line 19:  
=== Dependencies ===
 
=== Dependencies ===
   −
In addition to downloading the binary above (or compiling one yourself), you need *CRIU* installed on your system, with at least version 2.0. You also need some shared libraries on your system. The most likely things you'll need to install are *libprotobuf-c* and *libnl-3*. Here's an output of <code>ldd</code> on my system:
+
In addition to downloading the binary above (or compiling one yourself), you need '''CRIU''' installed on your system, with at least version 2.0. You also need some shared libraries on your system. The most likely things you'll need to install are '''libprotobuf-c''' and '''libnl-3'''. Here's an output of <code>ldd</code> on my system:
    
     # ldd `which criu`
 
     # ldd `which criu`
Line 51: Line 51:  
=== restore ===
 
=== restore ===
   −
Like *checkpoint*, *restore* is a top level command in this version of Docker. Continuing our example, let's restore the same container:
+
Like '''checkpoint''', '''restore''' is a top level command in this version of Docker. Continuing our example, let's restore the same container:
    
     docker restore looper
 
     docker restore looper
Line 57: Line 57:  
If we then print the logs, you should see they start from where we left off and continue to increase.  
 
If we then print the logs, you should see they start from where we left off and continue to increase.  
   −
==== Restoring into a *new* container ====
+
==== Restoring into a '''new''' container ====
    
Beyond the straightforward case of checkpointing and restoring the same container, it's also possible to checkpoint one container, and then restore the checkpoint into a completely different container. Right now that is done with the <code>--force</code> option, in conjunction with the <code>--image-dir</code> option. Here's a slightly revised example from before:
 
Beyond the straightforward case of checkpointing and restoring the same container, it's also possible to checkpoint one container, and then restore the checkpoint into a completely different container. Right now that is done with the <code>--force</code> option, in conjunction with the <code>--image-dir</code> option. Here's a slightly revised example from before:
21

edits