jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
runc/namespaces/nsenter
History
Andrey Vagin d572094b75 new-api: execute a process inside an existing container 
A new constructor function (like nsenter) is added in this patch.  This
function gets arguments from environment variables and its behaviour doesn't
depend on a command line arguments.

A program which calls factory.StartInitialization() must import the nsenter
package. It looks ugly, but I don't know another way how to enter into CT from
a go code.

Signed-off-by: Andrey Vagin <avagin@openvz.org>
 		2014-12-25 18:44:10 +03:00
..
README.md Move nsenter code into separate package 2014-08-08 10:42:19 -07:00
nsenter.c Set child sub reaper option on nsenter to help cleanup all processes orphaned via ExecIn. 2014-11-19 20:14:20 +00:00
nsenter.go new-api: execute a process inside an existing container 2014-12-25 18:44:10 +03:00
nsenter_unsupported.go Add unsupported file for cross compile 2014-08-08 12:14:48 -07:00
nsexec.c new-api: execute a process inside an existing container 2014-12-25 18:44:10 +03:00

README.md

nsenter

The nsenter package registers a special init constructor that is called before the Go runtime has a chance to boot. This provides us the ability to setns on existing namespaces and avoid the issues that the Go runtime has with multiple threads. This constructor is only called if this package is registered, imported, in your go application and the argv 0 is nsenter.