[CRIU] Docker checkpoint: real-world workloads

[Alice Frosi]

If the attachment does not work, please let me know and I will upload somewhere

On 22.09.2017 15:53, Ross Boucher wrote:

> Can you post the full dump and restore logs somewhere and link to them?
>
> On Fri, Sep 22, 2017 at 9:43 AM Alice Frosi <alice at linux.vnet.ibm.com 
> <mailto:alice at linux.vnet.ibm.com>> wrote:
>
>     Docker version:
>
>     Client:
>       Version:      17.10.0-dev
>       API version:  1.32
>       Go version:   go1.9
>       Git commit:
>       Built:        Thu Sep 21 10:13:54 2017
>       OS/Arch:      linux/s390x
>
>     Server:
>       Version:      17.06.0-dev
>       API version:  1.32 (minimum version 1.12)
>       Go version:   go1.8.3
>       Git commit:   e9cb25e967
>       Built:        Thu Sep 21 09:31:03 2017
>       OS/Arch:      linux/s390x
>       Experimental: true
>
>     Docker checkpoint commands:
>
>     docker checkpoint create CONTAINER_NAME checkpoint
>
>     docker start CONTAINER_NAME --checkpoint=checkpoint
>
>     Thanks for the help
>
>     Alice
>
>>     Could you share the version of Docker you were running, along
>>     with the commands you used to invoke the checkpoint and restore?
>>
>>     On Fri, Sep 22, 2017 at 8:05 AM Alice Frosi
>>     <alice at linux.vnet.ibm.com <mailto:alice at linux.vnet.ibm.com>> wrote:
>>
>>         Hi,
>>
>>         We have started to test docker checkpoint with a real-world
>>         workloads.
>>
>>         Until now we tried with acmeair-nodejs [1] with the
>>         microservice usecase.
>>
>>         This application creates 10 containers and they interact
>>         between each other with volumes and network
>>
>>         connection. The checkpoint war not successful. Here, the
>>         error message in restore:
>>
>>         (00.195135)      1: No iptables-9.img image
>>
>>         (00.195136)      1: Error (criu/include/image.h:144): BUG at
>>         criu/include/image.h:144
>>
>>         (00.195171) Error (criu/cr-restore.c:1284): 15638 killed by
>>         signal 127: Unknown signal 127
>>
>>         (00.315156) Error (criu/mount.c:2980): mnt: Can't remove the
>>         directory /tmp/.criu.mntns.C12otH: No such file or directory
>>
>>         (00.315160) Error (criu/cr-restore.c:2152): Restoring FAILED.
>>
>>         We tested with criu version:
>>
>>         Version: 3.4
>>
>>         GitID: v3.4-224-g3706af7b
>>
>>         1) Any ideas for what could have caused the error?
>>
>>         Additionally, we have two more general questions.
>>
>>         2) How should we perform checkpoint for applications with
>>         multiple container interaction?
>>
>>         3) For which use cases have you already tried the C/R?
>>
>>         We saw this overview in your wiki [2], but it seems to be not
>>         recently updated.
>>
>>         Regards
>>
>>         Alice Frosi
>>
>>         [1]
>>         https://github.com/blueperf/acmeair-nodejs/blob/master/README_Docker.md
>>         [2] https://criu.org/What_software_is_supported
>>
>>
>>
>>         _______________________________________________
>>         CRIU mailing list
>>         CRIU at openvz.org <mailto:CRIU at openvz.org>
>>         https://lists.openvz.org/mailman/listinfo/criu
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20170922/54b76c9f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dump.log
Type: text/x-log
Size: 163762 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20170922/54b76c9f/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: restore.log
Type: text/x-log
Size: 22095 bytes
Desc: not available
URL: <http://lists.openvz.org/pipermail/criu/attachments/20170922/54b76c9f/attachment-0003.bin>