tree: bce1819c5dd2dc6d06fca1033556e19a5a229fff [path history] [tgz]
  1. apparmor/
  2. cgroups/
  3. configs/
  4. criurpc/
  5. devices/
  6. hack/
  7. integration/
  8. label/
  9. nsenter/
  10. seccomp/
  11. selinux/
  12. stacktrace/
  13. system/
  14. user/
  15. utils/
  16. xattr/
  17. capabilities_linux.go
  18. compat_1.5_linux.go
  19. console.go
  20. console_freebsd.go
  21. console_linux.go
  22. console_windows.go
  23. container.go
  24. container_linux.go
  25. container_linux_test.go
  26. container_nouserns_linux.go
  27. container_userns_linux.go
  28. container_windows.go
  29. criu_opts_unix.go
  30. criu_opts_windows.go
  31. error.go
  32. error_test.go
  33. factory.go
  34. factory_linux.go
  35. factory_linux_test.go
  36. generic_error.go
  37. generic_error_test.go
  38. init_linux.go
  39. network_linux.go
  40. notify_linux.go
  41. notify_linux_test.go
  42. process.go
  43. process_linux.go
  45. restored_process.go
  46. rootfs_linux.go
  47. rootfs_linux_test.go
  48. setgroups_linux.go
  49. setns_init_linux.go
  51. standard_init_linux.go
  52. stats.go
  53. stats_freebsd.go
  54. stats_linux.go
  55. stats_windows.go

Libcontainer provides a native Go implementation for creating containers with namespaces, cgroups, capabilities, and filesystem access controls. It allows you to manage the lifecycle of the container performing additional operations after the container is created.


A container is a self contained execution environment that shares the kernel of the host system and which is (optionally) isolated from other containers in the system.

Using libcontainer

To create a container you first have to initialize an instance of a factory that will handle the creation and initialization for a container.

Because containers are spawned in a two step process you will need to provide arguments to a binary that will be executed as the init process for the container. To use the current binary that is spawning the containers and acting as the parent you can use os.Args[0] and we have a command called init setup.

root, err := libcontainer.New("/var/lib/container", libcontainer.InitArgs(os.Args[0], "init"))
if err != nil {

Once you have an instance of the factory created we can create a configuration struct describing how the container is to be created. A sample would look similar to this:

config := &configs.Config{
    Rootfs: rootfs,
    Capabilities: []string{
    Namespaces: configs.Namespaces([]configs.Namespace{
        {Type: configs.NEWNS},
        {Type: configs.NEWUTS},
        {Type: configs.NEWIPC},
        {Type: configs.NEWPID},
        {Type: configs.NEWNET},
    Cgroups: &configs.Cgroup{
        Name:            "test-container",
        Parent:          "system",
        AllowAllDevices: false,
        AllowedDevices:  configs.DefaultAllowedDevices,

    Devices:  configs.DefaultAutoCreatedDevices,
    Hostname: "testing",
    Networks: []*configs.Network{
            Type:    "loopback",
            Address: "",
            Gateway: "localhost",
    Rlimits: []configs.Rlimit{
            Type: syscall.RLIMIT_NOFILE,
            Hard: uint64(1024),
            Soft: uint64(1024),

Once you have the configuration populated you can create a container:

container, err := root.Create("container-id", config)

To spawn bash as the initial process inside the container and have the processes pid returned in order to wait, signal, or kill the process:

process := &libcontainer.Process{
    Args:   []string{"/bin/bash"},
    Env:    []string{"PATH=/bin"},
    User:   "daemon",
    Stdin:  os.Stdin,
    Stdout: os.Stdout,
    Stderr: os.Stderr,

err := container.Start(process)
if err != nil {

// wait for the process to finish.
status, err := process.Wait()
if err != nil {

// destroy the container.

Additional ways to interact with a running container are:

// return all the pids for all processes running inside the container.
processes, err := container.Processes()

// get detailed cpu, memory, io, and network statistics for the container and
// it's processes.
stats, err := container.Stats()

// pause all processes inside the container.

// resume all paused processes.

Checkpoint & Restore

libcontainer now integrates CRIU for checkpointing and restoring containers. This let's you save the state of a process running inside a container to disk, and then restore that state into a new process, on the same machine or on another machine.

criu version 1.5.2 or higher is required to use checkpoint and restore. If you don't already have criu installed, you can build it from source, following the online instructions. criu is also installed in the docker image generated when building libcontainer with docker.

Copyright and license

Code and documentation copyright 2014 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.