[CRIU] system configuration for dumping/restoring LXC

[Krystof Zmudzinski]

Thanks for the fast reply.  I will reinstall Ubuntu 14.04, LXC tools and criu-1.3 as before.  I will let you know what I had to do along the way when I encounter problems.  Maybe at the end you will be able to post this somewhere on your website for somebody like me who is not a Linux expert. :-)

Speaking of not being a Linux expert, I'm not sure if I understand the point about the rootfs mounts.  I do recall that one of the error messages on restore was something about same rootfs can't be used so I can see how it makes sense what you said about different rootfs there.  But I don't understand how the configuration on the website can work when lxc-create is executed.

Krystof
 

________________________________
 From: Andrey Wagin <avagin at gmail.com>
To: Krystof Zmudzinski <krystof_zmudzinski at yahoo.com> 
Cc: "criu at openvz.org" <criu at openvz.org> 
Sent: Wednesday, September 10, 2014 11:59 PM
Subject: Re: system configuration for dumping/restoring LXC
  




Hi Krystof,

I added criu at openvz.org in CC


2014-09-11 5:03 GMT+04:00 Krystof Zmudzinski <krystof_zmudzinski at yahoo.com>:

Andrew,
>
>
>I've spent some time trying to build a system, which would allow me to dump and restore a Linux container using criu.  I started by reading instructions on this page LXC but the information seems buggy.  For example, test-lxc.conf has these 2 seemingly incompatible lines in it:
>lxc.mount = /root/test-lxc/etc/fstab
>lxc.rootfs = /root/test-lxc-root/
>
>
>So is the rootfs in /root/test-lxc or /root/test-lxc-root>

It can't be buggy, because I have copied this config from my test node. I think you can use  /root/test-lxc and don't bind-mount /root/test-lxc to /root/test-lxc-root, but you will need to do this bind-mount to restore the CT.


>
>When I tried executing lxc-create -n test-lxc -f test-lxc.conf with the configuration as presented on that page, lxc-create failed.  When I changed rootfs to /root/test-lxc everywhere, it worked.  I was even able to dump the container using the criu-1.3 but restore never worked.  That was on Ubuntu 14.04.  When I switched to Fedora 20, even dump didn't work.

If you are able to dump the CT, you must able to restore it. If you can't to do that, it's bug and we are ready to fix it. So could you show how you execute criu and logs from "criu dump" and "criu restore"?





>
>I don't really care what system I have to use and how simple my container is.  I can tell that there are other people on the net who talk about successfully dumping and restoring containers but I can't figure out what system/container configurations they use.
>
>
>Could you provide me with a pointer to the host configuration and container configuration -- even if I have to go some older versions -- that allow for a successful dump/restore of a Linux container?
>
>
>BTW, I have been able to use criu-1.3 to dump/restore single processes.
>
>
>Thanks in adavance,
>
>
>Krystof
>
>
>
>
>
> 
>
> 
> 
> 
> 
> 
>LXC
>This article describes how to perform checkpoint-restore for an LXC container.  
>View on criu.org Preview by Yahoo  
>
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20140911/8238966c/attachment-0001.html>