Changes

Jump to navigation Jump to search
432 bytes added ,  10:49, 6 November 2018
Line 1: Line 1: −
An resource is called "external", if it can't be dumped and restored without external help. Usually this mean that a part of it state is out of a dumped container.
+
An resource is called "external", if it can't be dumped and restored without some help from the caller. Usually this mean that a part of it state is out of a dumped container.
   −
The general approach is to enumerate all such resources on dump and set one of restoring strategies for each of them on restore. An approach how to restore an resource may be different for different types of resources.
+
== Dump ==
 +
 
 +
Typically external resources are just told to be such on dump. The respective option looks like <code>--external ''TYPE''[''ID'']:''VAL''</code> option, where <code>''TYPE''</code> is resource type, <code>''ID''</code> is resource ID and <code>''VAL''</code> is optional argument.
 +
 
 +
== Restore ==
 +
 
 +
Restoring external resources heavily depends on its type. Some resources can be restored by CRIU itself with the help of <code>--external</code> option, some cannot. See below for further details.
 +
 
 +
== Resource types ==
 +
 
 +
The following external resources can be checkpointed and restored:
    
* [[External bind mounts]]
 
* [[External bind mounts]]
 +
* [[External mount devices]]
 
* [[External files]]
 
* [[External files]]
 
* [[External UNIX socket]]
 
* [[External UNIX socket]]
 +
* [[VETH device]]
 +
* [[Mac-Vlan]]
 +
* [[External net namespaces]]
 +
 +
== See also ==
   −
All of them are controlled with the <code>--external ID</code> option.
+
* [[Shell jobs]]
   −
[[Category:Empty articles]]
+
[[Category:API]]
 
[[Category:External]]
 
[[Category:External]]

Navigation menu