jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

add binary target to direct install in a container 

This add `make binary` to perform direct install libcontainer binaries inside
dockercore/libcontainer container instead of having to install dependencies and
run `make direct-install` on the host.

The `nsinit` binary will be placed into `bundles/nsinit`, and we ignore the
bundles directory from git.

Signed-off-by: Daniel, Dao Quang Minh <dqminh89@gmail.com>
This commit is contained in:
Daniel, Dao Quang Minh 2015-03-28 07:32:03 +00:00
parent af371eae76
commit c4a8de8de0
3 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.gitignore vendored
View File

@ -1 +1,2 @@
bundles
nsinit/nsinit nsinit/nsinit

2
Makefile
View File

@ -29,3 +29,5 @@ local:
validate: validate:
hack/validate.sh hack/validate.sh
binary: all
docker run --rm --privileged -v $(CURDIR)/bundles:/go/bin dockercore/libcontainer make direct-install

3
README.md
View File

@ -141,6 +141,9 @@ container.Resume()
It is able to spawn new containers or join existing containers. A root It is able to spawn new containers or join existing containers. A root
filesystem must be provided for use along with a container configuration file. filesystem must be provided for use along with a container configuration file.
To build `nsinit`, run `make binary`. It will save the binary into
`bundles/nsinit`.
To use `nsinit`, cd into a Linux rootfs and copy a `container.json` file into To use `nsinit`, cd into a Linux rootfs and copy a `container.json` file into
the directory with your specified configuration. Environment, networking, the directory with your specified configuration. Environment, networking,
and different capabilities for the container are specified in this file. and different capabilities for the container are specified in this file.