Name: opencontainers-runc
Owner: OpenShift
Description: CLI tool for spawning and running containers according to the OCI specification
Forked from: opencontainers/runc
Created: 2017-09-29 19:26:47.0
Updated: 2017-09-29 19:27:01.0
Pushed: 2018-04-07 20:15:24.0
Homepage: https://www.opencontainers.org/
Size: 6247
Language: Go
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
[![Build Status](https://jenkins.dockerproject.org/buildStatus/icon?job=runc Master)](https://jenkins.dockerproject.org/job/runc Master)
runc
is a CLI tool for spawning and running containers according to the OCI specification.
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.
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.
eate a 'github.com/opencontainers' in your GOPATH/src
ithub.com/opencontainers
clone https://github.com/opencontainers/runc
unc
make install
runc
will be installed to /usr/local/sbin/runc
on your system.
In order to enable seccomp support you will need to install libseccomp on your platform.
If you do not want to build runc
with seccomp support you can add BUILDTAGS=""
when running make.
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.
BUILDTAGS='seccomp apparmor'
| Build Tag | Feature | Dependency |
|———–|————————————|————-|
| seccomp | Syscall filtering | libseccomp |
| selinux | selinux process and mount labeling |
runc
currently supports running its test suite via Docker.
To run the suite just type make test
.
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.
ke test TESTFLAGS="-run=SomeTestFunction"
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.
eate the top most bundle directory
r /mycontainer
mycontainer
eate the rootfs directory
r rootfs
port busybox via Docker into the rootfs directory
er 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.
spec
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.
mycontainer
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 move power of 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": [
"CAP_AUDIT_WRITE",
"CAP_KILL",
"CAP_NET_BIND_SERVICE"
],
"rlimits": [
{
"type": "RLIMIT_NOFILE",
"hard": 1024,
"soft": 1024
}
],
"noNewPrivileges": true
},
Now we can go though the lifecycle operations in your shell.
mycontainer
create mycontainerid
ew the container is created and in the "created" state
list
art the process inside the container
start mycontainerid
ter 5 seconds view that the container has exited and is now in the stopped state
list
w delete the container
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.
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.
t]
ription=Start My Container
vice]
=forking
Start=/usr/local/sbin/runc run -d --pid-file /run/mycontainerid.pid mycontainerid
StopPost=/usr/local/sbin/runc delete mycontainerid
ingDirectory=/mycontainer
ile=/run/mycontainerid.pid
tall]
edBy=multi-user.target