<div dir="ltr"><div>Thank you, Tycho. <br></div>Do you have any idea how to start a process in the container and it is the child of the container's init? <br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 11, 2015 at 11:40 AM, Tycho Andersen <span dir="ltr"><<a href="mailto:tycho.andersen@canonical.com" target="_blank">tycho.andersen@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span class=""><br>
On Fri, Sep 11, 2015 at 11:21:17AM -0400, Tina Li wrote:<br>
> Hi all,<br>
> I am trying to checkpoint/restore the container using the following<br>
> commands.<br>
> sudo lxc-checkpoint -s -D /tmp/checkpoint -n mycontainer<br>
> sudo lxc-checkpoint -r -D /tmp/checkpoint -n mycontainer<br>
> The lxc-checkpoint command will invoke criu to do checkpoint and restore.<br>
> I have some doubts:<br>
> 1) After restoring the container, why all the process pids related to the<br>
> container are changed?<br>
> E.g. before checkpoint, the PID of container is 1385, but after restore the<br>
> PID of the container is 3089. (1385 is not occupied by other process.)<br>
<br>
</span>The pids in the host pid namespace are different, but in the<br>
container's pid namespace they are the same.<br>
<span class=""><br>
> 2) If I use lxc-attach to enter the container, and run a process in it.<br>
> Then when checkpoint the container, the process is stopped, but when<br>
> restore the container, the process is not resumed. Does anyone know why?<br>
<br>
</span>Processes started by lxc-attach aren't children of the container's<br>
init, which likely confuses criu.<br>
<span class="HOEnZb"><font color="#888888"><br>
Tycho<br>
</font></span></blockquote></div><br></div>