Difference between revisions of "Action scripts"
Jump to navigation
Jump to search
(minor formatting and English fixes) |
(link to docker; don't link twice) |
||
| Line 2: | Line 2: | ||
;<code>network-lock</code> | ;<code>network-lock</code> | ||
| − | : request to lock a container network (used by Docker and [[LXC]]) | + | : request to lock a container network (used by [[Docker]] and [[LXC]]) |
;<code>network-unlock</code> | ;<code>network-unlock</code> | ||
| − | : requested to unlock a container network (used by Docker and | + | : requested to unlock a container network (used by Docker and LXC) |
;<code>post-dump</code> | ;<code>post-dump</code> | ||
Revision as of 16:33, 8 April 2015
With the --action-script command line option, CRIU can call your action scripts (also known as hooks) at various stages of dumping/restoring. The following hooks are available:
network-unlock- requested to unlock a container network (used by Docker and LXC)
post-dump- called when CRIU finished dumping tasks before unfreezing them
post-restore- called when CRIU has finished restoring tasks before unlocking the network
setup-namespaces- called when the root task is alive and new set of namespaces is created to set them up
CLI
These hooks are added with the --action-script shell-code-to-execute option. When called, the CRTOOLS_SCRIPT_ACTION environment is set to a value determining which type of action is performed.
RPC
In case of RPC, action scripts are implemented as notifications. Once CRIU service wants to execute a script, it sends an RPC message to the caller and waits for it to respond with criu_req message having notify_success = true.
Library
When using a library, one can set up a callback using the criu_set_notify routine.