[CRIU] problem with CRIU

[Marco BROCANELLI]

Never mind for the problem of CRIU (tainted). I have upgraded CRIU from 3.6 to 3.10, which have fixed the problem. Now all the checks say “looks good.”

However, I still have the following issue: when I try to restore a checkpoint, I get the following error

“Error response from daemon: failed to retrieve OCI runtime container pid: open /run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/7400b12f7ce1da658d44da9349893f40ff7ae512d0479fe116df16c399f1f741/init.pid: no such file or directory: unknown”

How can I fix this problem?

I am running on Ubuntu 18.04 (running via Parallels on MacOS). CRIU version: 3.10. Docker version: “Version: 18.06.1-ce , API version: 1.38”.


Thank you so much for the help.
Marco
--------------------------------------------------------------------------------------------------
Marco Brocanelli, Ph.D.,
Assistant Professor,
Department of Computer Science,
Wayne State University,
https://engineering.wayne.edu/profile/gt2504
--------------------------------------------------------------------------------------------------


From: Marco BROCANELLI <brok at wayne.edu>
Date: Friday, October 12, 2018 at 4:30 PM
To: "criu at openvz.org" <criu at openvz.org>
Subject: problem with CRIU

Hi,
I have installed CRIU (v. 3.6) and run the check. Here are the results:


  *   “criu check” -> looks good
  *   “criu check --extra” -> looks good
  *   “criu check --all” -> “Warn  (criu/cr-check.c:1029): CRIU built without CONFIG_COMPAT - can't C/R ia32. Looks good but some kernel features are missing which, depending on your process tree, may cause dump or restore failure.” How do I fix this? I run the zdtm test and got “The kernel is tainted:..” Do I get the warning from criu check –all because my kernel is tainted?

I have been trying to checkpoint and restore but at the time of the restore I always get the error: “Error response from daemon: failed to retrieve OCI runtime container pid:…”

Are the two problems related? I followed the example available here for the checkpointing: https://criu.org/Docker

The experimental feature is enabled in both client and server. The checkpoint file is correctly created. However, I have also noticed that the looper in the example does NOT stop after issuing the command “docker checkpoint create looper checkpoint1”. According to the above guide it should stop, right?

Can you please help me debug this?

I am running on Ubuntu 18.04 (running via Parallels on MacOS). CRIU version: 3.6. Docker version: “Version: 18.06.1-ce , API version: 1.38”.

Thank you so much for any suggestions,
Marco

--------------------------------------------------------------------------------------------------
Marco Brocanelli, Ph.D.,
Assistant Professor,
Department of Computer Science,
Wayne State University,
https://engineering.wayne.edu/profile/gt2504
--------------------------------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20181012/9641840a/attachment-0001.html>