Difference between revisions of "External resources"
Jump to navigation
Jump to search
(slight rewording) |
Anuj.kumar (talk | contribs) m |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | A resource is called "external", if it can't be dumped and restored without some help from the caller. Usually this means that a part of its state is out of a dumped container. | |
== Dump == | == Dump == | ||
| Line 19: | Line 19: | ||
* [[VETH device]] | * [[VETH device]] | ||
* [[Mac-Vlan]] | * [[Mac-Vlan]] | ||
| + | * [[External net namespaces]] | ||
== See also == | == See also == | ||
Latest revision as of 11:34, 17 March 2020
A resource is called "external", if it can't be dumped and restored without some help from the caller. Usually this means that a part of its state is out of a dumped container.
Dump[edit]
Typically external resources are just told to be such on dump. The respective option looks like --external TYPE[ID]:VAL option, where TYPE is resource type, ID is resource ID and VAL is optional argument.
Restore[edit]
Restoring external resources heavily depends on its type. Some resources can be restored by CRIU itself with the help of --external option, some cannot. See below for further details.
Resource types[edit]
The following external resources can be checkpointed and restored:
- External bind mounts
- External mount devices
- External files
- External UNIX socket
- VETH device
- Mac-Vlan
- External net namespaces