2,257
edits
Changes
Jump to navigation
Jump to search
Line 65:
Line 65: − --evasive-devices # handle /dev/log usage bug Line 75:
Line 74: − --evasive-devices Line 86:
Line 84: + +
→Dump and restore
<pre>
<pre>
crtools dump
crtools dump
--tcp-established # allow for TCP connections dump
--tcp-established # allow for TCP connections dump
-n net -n mnt -n ipc -n pid # dump all the namespaces container uses
-n net -n mnt -n ipc -n pid # dump all the namespaces container uses
<pre>
<pre>
crtools restore
crtools restore
--tcp-established
--tcp-established
-n net -n mnt -n ipc -n pid
-n net -n mnt -n ipc -n pid
We also find it useful to use the <code>--restore-detached</code> option for restore to make contianer reparent to init rather than hanging on a crtools process launched from shell. Another useful option is the <code>--pidfile</code> one -- you will be able to find out the host-side pid of a container init after restore.
We also find it useful to use the <code>--restore-detached</code> option for restore to make contianer reparent to init rather than hanging on a crtools process launched from shell. Another useful option is the <code>--pidfile</code> one -- you will be able to find out the host-side pid of a container init after restore.
Also note, that there's a BUG in how LXC prepares the /dev filesystem for a container which sometimes makes it impossible to dump and container. The <code>--evasive-devices</code> option can help.
More details on the option mentioned can be found in [[Usage]] and [[Advanced usage]] pages.
More details on the option mentioned can be found in [[Usage]] and [[Advanced usage]] pages.