For a basic description about checkpointing and restoring containers with
runc
please see runc-checkpoint(8) and
runc-restore(8).
In addition to specifying options on the command-line like it is described in the man-pages (see above), it is also possible to influence CRIU's behaviour using CRIU configuration files. For details about CRIU's configuration file support please see CRIU's wiki.
In addition to CRIU's default configuration files runc
tells CRIU to
also evaluate the file /etc/criu/runc.conf
. Using the annotation
org.criu.config
it is, however, possible to change this additional
CRIU configuration file.
If the annotation org.criu.config
is set to an empty string runc
will not pass any additional configuration file to CRIU. With an empty
string it is therefore possible to disable the additional CRIU configuration
file. This can be used to make sure that no additional configuration file
changes CRIU's behaviour accidentally.
If the annotation org.criu.config
is set to a non-empty string runc
will
pass that string to CRIU to be evaluated as an additional configuration file.
If CRIU cannot open this additional configuration file, it will ignore this
file and continue.
{
"ociVersion": "1.0.0",
"annotations": {
"org.criu.config": ""
},
"process": {
{
"ociVersion": "1.0.0",
"annotations": {
"org.criu.config": "/etc/special-runc-criu-options"
},
"process": {
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。