CLI tool for spawning and running containers according to the OCI specification
Go Shell C Makefile
Latest commit 74a1729 Oct 20, 2017 @hqhq hqhq Merge pull request #1607 from crosbymichael/term-err
libcontainer: handler errors from terminate
Permalink
Failed to load latest commit information.
contrib Set ClearONLCR in tests Sep 25, 2017
libcontainer Merge pull request #1607 from crosbymichael/term-err Oct 20, 2017
man Use Int64SliceFlag instead of StringFlag to get additional gids. Oct 10, 2017
script release: import umoci's release.sh script Aug 16, 2017
tests Merge pull request #1608 from crosbymichael/gids Oct 16, 2017
vendor Vendor updated libseccomp-golang for bugfix Oct 10, 2017
.gitignore move from Godeps to vndr Feb 24, 2017
.pullapprove.yml Disallow self-LGTMs Jun 1, 2016
.travis.yml Update Travis config to use trusty-backports libseccomp Oct 10, 2017
CONTRIBUTING.md *: add information about security mailing list Dec 3, 2016
Dockerfile tests: add tests for rootless multi-mapping configurations Sep 9, 2017
LICENSE Initial commit of runc binary Jun 22, 2015
MAINTAINERS Remove @avagin as a maintainer Aug 2, 2017
MAINTAINERS_GUIDE.md trailing punctuation in header Dec 2, 2016
Makefile Add `-installsuffix netgo` in static build Sep 11, 2017
NOTICE Move libcontainer documenation to root of repo Jun 26, 2015
PRINCIPLES.md Move libcontainer documenation to root of repo Jun 26, 2015
README.md README.md: adjust capabilities section in config.json example Jul 25, 2017
VERSION VERSION: back to development Aug 2, 2017
checkpoint.go checkpoint: support lazy migration Sep 6, 2017
create.go Prepare startContainer() to have more action May 1, 2017
delete.go Moving the rest of runc to x/sys/unix May 22, 2017
events.go libcontainer: add support for Intel RDT/CAT in runc Sep 1, 2017
exec.go Check for negative gid Oct 11, 2017
init.go runc only works on Linux so remove putative Solaris and unsupported main Jun 29, 2017
kill.go Put signalMap in a separate file, so it may be arch-specific Jun 2, 2017
list.go list: stop casting unknown UIDs to their unicode values Jul 11, 2017
main.go main: honor XDG_RUNTIME_DIR for rootless containers Sep 9, 2017
notify_socket.go Updated logrus to v1 Jul 19, 2017
pause.go Only allow single container operation Mar 8, 2017
ps.go runc: add support for rootless containers Mar 23, 2017
restore.go checkpoint: support lazy migration Sep 6, 2017
rlimit_linux.go error strings should not be capitalized or end with punctuation Dec 1, 2016
run.go Prepare startContainer() to have more action May 1, 2017
signalmap.go Add support for mips/mips64 Jun 2, 2017
signalmap_mipsx.go Add support for mips/mips64 Jun 2, 2017
signals.go signal: ignore tty.resize errors Aug 26, 2017
spec.go Delete unused function Sep 8, 2017
start.go Only allow single container operation Mar 8, 2017
state.go Check args numbers before application start Nov 29, 2016
tty.go Set ClearONLCR in tests Sep 25, 2017
update.go intelrdt: add update command support Sep 19, 2017
utils.go Updated logrus to v1 Jul 19, 2017
utils_linux.go Set initial console size based on process spec Oct 4, 2017
vendor.conf Vendor updated libseccomp-golang for bugfix Oct 10, 2017

README.md

runc

Build Status Go Report Card GoDoc

Introduction

runc is a CLI tool for spawning and running containers according to the OCI specification.

Releases

runc depends on and tracks the runtime-spec repository. We will try to make sure that runc and the OCI specification major versions stay in lockstep. This means that runc 1.0.0 should implement the 1.0 version of the specification.

You can find official releases of runc on the release page.

Security

If you wish to report a security issue, please disclose the issue responsibly to security@opencontainers.org.

Building

runc currently supports the Linux platform with various architecture support. It must be built with Go version 1.6 or higher in order for some features to function properly.

In order to enable seccomp support you will need to install libseccomp on your platform.

e.g. libseccomp-devel for CentOS, or libseccomp-dev for Ubuntu

Otherwise, if you do not want to build runc with seccomp support you can add BUILDTAGS="" when running make.

# create a 'github.com/opencontainers' in your GOPATH/src
cd github.com/opencontainers
git clone https://github.com/opencontainers/runc
cd runc

make
sudo make install

runc will be installed to /usr/local/sbin/runc on your system.

Build Tags

runc supports optional build tags for compiling support of various features. To add build tags to the make option the BUILDTAGS variable must be set.

make BUILDTAGS='seccomp apparmor'
Build Tag Feature Dependency
seccomp Syscall filtering libseccomp
selinux selinux process and mount labeling
apparmor apparmor profile support libapparmor
ambient ambient capability support kernel 4.3

Running the test suite

runc currently supports running its test suite via Docker. To run the suite just type make test.

make test

There are additional make targets for running the tests outside of a container but this is not recommended as the tests are written with the expectation that they can write and remove anywhere.

You can run a specific test case by setting the TESTFLAGS variable.

# make test TESTFLAGS="-run=SomeTestFunction"

Dependencies Management

runc uses vndr for dependencies management. Please refer to vndr for how to add or update new dependencies.

Using runc

Creating an OCI Bundle

In order to use runc you must have your container in the format of an OCI bundle. If you have Docker installed you can use its export method to acquire a root filesystem from an existing Docker container.

# create the top most bundle directory
mkdir /mycontainer
cd /mycontainer

# create the rootfs directory
mkdir rootfs

# export busybox via Docker into the rootfs directory
docker export $(docker create busybox) | tar -C rootfs -xvf -

After a root filesystem is populated you just generate a spec in the format of a config.json file inside your bundle. runc provides a spec command to generate a base template spec that you are then able to edit. To find features and documentation for fields in the spec please refer to the specs repository.

runc spec

Running Containers

Assuming you have an OCI bundle from the previous step you can execute the container in two different ways.

The first way is to use the convenience command run that will handle creating, starting, and deleting the container after it exits.

# run as root
cd /mycontainer
runc run mycontainerid

If you used the unmodified runc spec template this should give you a sh session inside the container.

The second way to start a container is using the specs lifecycle operations. This gives you more power over how the container is created and managed while it is running. This will also launch the container in the background so you will have to edit the config.json to remove the terminal setting for the simple examples here. Your process field in the config.json should look like this below with "terminal": false and "args": ["sleep", "5"].

        "process": {
                "terminal": false,
                "user": {
                        "uid": 0,
                        "gid": 0
                },
                "args": [
                        "sleep", "5"
                ],
                "env": [
                        "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                        "TERM=xterm"
                ],
                "cwd": "/",
                "capabilities": {
                        "bounding": [
                                "CAP_AUDIT_WRITE",
                                "CAP_KILL",
                                "CAP_NET_BIND_SERVICE"
                        ],
                        "effective": [
                                "CAP_AUDIT_WRITE",
                                "CAP_KILL",
                                "CAP_NET_BIND_SERVICE"
                        ],
                        "inheritable": [
                                "CAP_AUDIT_WRITE",
                                "CAP_KILL",
                                "CAP_NET_BIND_SERVICE"
                        ],
                        "permitted": [
                                "CAP_AUDIT_WRITE",
                                "CAP_KILL",
                                "CAP_NET_BIND_SERVICE"
                        ],
                        "ambient": [
                                "CAP_AUDIT_WRITE",
                                "CAP_KILL",
                                "CAP_NET_BIND_SERVICE"
                        ]
                },
                "rlimits": [
                        {
                                "type": "RLIMIT_NOFILE",
                                "hard": 1024,
                                "soft": 1024
                        }
                ],
                "noNewPrivileges": true
        },

Now we can go through the lifecycle operations in your shell.

# run as root
cd /mycontainer
runc create mycontainerid

# view the container is created and in the "created" state
runc list

# start the process inside the container
runc start mycontainerid

# after 5 seconds view that the container has exited and is now in the stopped state
runc list

# now delete the container
runc delete mycontainerid

This adds more complexity but allows higher level systems to manage runc and provides points in the containers creation to setup various settings after the container has created and/or before it is deleted. This is commonly used to setup the container's network stack after create but before start where the user's defined process will be running.

Rootless containers

runc has the ability to run containers without root privileges. This is called rootless. You need to pass some parameters to runc in order to run rootless containers. See below and compare with the previous version. Run the following commands as an ordinary user:

# Same as the first example
mkdir ~/mycontainer
cd ~/mycontainer
mkdir rootfs
docker export $(docker create busybox) | tar -C rootfs -xvf -

# The --rootless parameter instructs runc spec to generate a configuration for a rootless container, which will allow you to run the container as a non-root user.
runc spec --rootless

# The --root parameter tells runc where to store the container state. It must be writable by the user.
runc --root /tmp/runc run mycontainerid

Supervisors

runc can be used with process supervisors and init systems to ensure that containers are restarted when they exit. An example systemd unit file looks something like this.

[Unit]
Description=Start My Container

[Service]
Type=forking
ExecStart=/usr/local/sbin/runc run -d --pid-file /run/mycontainerid.pid mycontainerid
ExecStopPost=/usr/local/sbin/runc delete mycontainerid
WorkingDirectory=/mycontainer
PIDFile=/run/mycontainerid.pid

[Install]
WantedBy=multi-user.target