Changes

164 bytes added ,  13:57, 25 October 2016
no edit summary
Line 28: Line 28:  
which will mean, that the mountpoint /bar has inaccessible root.
 
which will mean, that the mountpoint /bar has inaccessible root.
   −
To dump and restore them there's the <code>--ext-mount-map KEY:VAL</code> option that sets up external mounts root mapping.
+
To dump and restore them there's the <code>--external mnt[KEY]:VAL</code> option that sets up external mounts root mapping.
    
On dump, KEY is a mountpoint inside container and correspoding VAL is a string that will be written into the image as mountpoint's root value.
 
On dump, KEY is a mountpoint inside container and correspoding VAL is a string that will be written into the image as mountpoint's root value.
Line 36: Line 36:  
For example, if we want to dump the task above we should call
 
For example, if we want to dump the task above we should call
   −
  criu dump ... --ext-mount-map /bar:barmount
+
  criu dump ... --external mnt[/bar]:barmount
    
The word <code>barmount</code> is an arbitrary identifier, that will be put in the image file instead of the original root path
 
The word <code>barmount</code> is an arbitrary identifier, that will be put in the image file instead of the original root path
Line 45: Line 45:  
On restore we should tell CRIU where to bind mount the <code>barmount</code> from like this
 
On restore we should tell CRIU where to bind mount the <code>barmount</code> from like this
   −
  criu restore ... --ext-mount-map barmount:/foo
+
  criu restore ... --external mnt[barmount]:/foo
    
With this CRIU will bind mount the /foo into proper mountpoint.
 
With this CRIU will bind mount the /foo into proper mountpoint.
Line 52: Line 52:     
FIXME
 
FIXME
 +
 +
== Old days ==
 +
 +
For now the same behavior is configured with the <code>--ext-mount-map KEY:VAL</code> option. Soon this option will be [[deprecation|deprecated]].
    
[[Category:HOWTO]]
 
[[Category:HOWTO]]
 
[[Category:External]]
 
[[Category:External]]