2,257
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: + + + +
no edit summary
When you restore a process tree with <code>-n/--namespaces pid</code> option the pid of a new task will be generated by the system (since the pids sitting in image files are treated as virtual, i.e. seen in namespace ones). To find this pid out you can use the <code>--pidfile <file></code> option to make crtools put the new pid into a pidfile.
When you restore a process tree with <code>-n/--namespaces pid</code> option the pid of a new task will be generated by the system (since the pids sitting in image files are treated as virtual, i.e. seen in namespace ones). To find this pid out you can use the <code>--pidfile <file></code> option to make crtools put the new pid into a pidfile.
== Restoring a veth pair of devices ==
When you restore a net namespace with a veth device end in it, crtools will create the other end of the pair in the net namespace you launch crtools from. By default it's name will be the one generated by veth kernel driver. Not to scan through all the net devices trying to fine one you can use the <code>--veth-pair <ns-dev>:<host-dev></code> option. When used a device named <code><ns-dev></code> in a newly restored namespace will be linked with the <code><host-dev></code> one in the crtools namespace.