From b7219cc2b34588e523eb0a53f1f69c7eacdb6d60 Mon Sep 17 00:00:00 2001 From: Peng Gao Date: Sat, 14 May 2016 22:37:46 +0800 Subject: [PATCH] Update nsenter README Signed-off-by: Peng Gao --- libcontainer/nsenter/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libcontainer/nsenter/README.md b/libcontainer/nsenter/README.md index d1a60ef98..32a2fc322 100644 --- a/libcontainer/nsenter/README.md +++ b/libcontainer/nsenter/README.md @@ -10,8 +10,8 @@ The `nsenter` package will `import "C"` and it uses [cgo](https://golang.org/cmd package. In cgo, if the import of "C" is immediately preceded by a comment, that comment, called the preamble, is used as a header when compiling the C parts of the package. So every time we import package `nsenter`, the C code function `nsexec()` would be -called. And package `nsenter` is now only imported in Docker execdriver, so every time -before we call `execdriver.Exec()`, that C code would run. +called. And package `nsenter` is now only imported in `main_unix.go`, so every time +before we call `cmd.Start` on linux, that C code would run. `nsexec()` will first check the environment variable `_LIBCONTAINER_INITPID` which will give the process of the container that should be joined. Namespaces fd will