pkg/libcontainer
Michael Crosby 3e5d25eca6 Remove container.json from readme
No need to duplicate this information when we already have a
container.json file in the root of libcontainer
Docker-DCO-1.1-Signed-off-by: Michael Crosby <michael@crosbymichael.com> (github: crosbymichael)
2014-04-30 18:52:15 -07:00
..
console Move rest of console functions to pkg 2014-04-24 10:35:20 -07:00
mount Add mountlabel to dev 2014-04-29 03:41:44 -07:00
network Fix libcontainer network support on rhel6 2014-04-09 15:44:18 +02:00
nsinit Make native driver use Exec func with different CreateCommand 2014-04-30 18:49:24 -07:00
security Ignore isnot exists errors for proc paths 2014-04-24 10:35:20 -07:00
utils Refactor and improve libcontainer and driver 2014-02-24 21:11:52 -08:00
container.go Move mounts into types.go 2014-04-24 10:35:20 -07:00
container.json Updated sample config to be usable. We should change the namespace 2014-04-25 21:10:23 +00:00
container_test.go Merge branch 'master' into libcontainer-fixes 2014-04-28 23:04:04 +00:00
MAINTAINERS Update email + add self to pkg/signal 2014-03-10 20:26:45 -07:00
README.md Remove container.json from readme 2014-04-30 18:52:15 -07:00
TODO.md Update libcontainer readme and todo list 2014-03-13 15:18:08 -07:00
types.go Move mounts into types.go 2014-04-24 10:35:20 -07:00
types_linux.go Dont use custom marshaling for caps and namespaces 2014-03-20 23:09:01 +00:00
types_test.go Avoid "invalid memory address or nil pointer dereference" panic 2014-04-10 22:07:29 +09:00

libcontainer - reference implementation for containers

background

libcontainer specifies configuration options for what a container is. It provides a native Go implementation for using Linux namespaces with no external dependencies. libcontainer provides many convenience functions for working with namespaces, networking, and management.

container

A container is a self contained directory that is able to run one or more processes without affecting the host system. The directory is usually a full system tree. Inside the directory a container.json file is placed with the runtime configuration for how the processes should be contained and ran. Environment, networking, and different capabilities for the process are specified in this file. The configuration is used for each process executed inside the container.

See the container.json file for what the configuration should look like.

Using this configuration and the current directory holding the rootfs for a process, one can use libcontainer to exec the container. Running the life of the namespace, a pid file is written to the current directory with the pid of the namespaced process to the external world. A client can use this pid to wait, kill, or perform other operation with the container. If a user tries to run a new process inside an existing container with a live namespace, the namespace will be joined by the new process.

You may also specify an alternate root place where the container.json file is read and where the pid file will be saved.

nsinit

nsinit is a cli application used as the reference implementation of libcontainer. It is able to spawn or join new containers giving the current directory. To use nsinit cd into a Linux rootfs and copy a container.json file into the directory with your specified configuration.

To execute /bin/bash in the current directory as a container just run:

nsinit exec /bin/bash

If you wish to spawn another process inside the container while your current bash session is running just run the exact same command again to get another bash shell or change the command. If the original process dies, PID 1, all other processes spawned inside the container will also be killed and the namespace will be removed.

You can identify if a process is running in a container by looking to see if pid is in the root of the directory.