This configuration file contains metadata necessary to implement standard operations against the container. This includes the process to run, environment variables to inject, sandboxing features to use, etc.
The canonical schema is defined in this document, but there is a JSON Schema in schema/config-schema.json
and Go bindings in specs-go/config.go
.
Platform-specific configuration schema are defined in the platform-specific documents linked below.
For properties that are only defined for some platforms, the Go property has a platform
tag listing those protocols (e.g. platform:"linux,solaris"
).
Below is a detailed description of each field defined in the configuration format and valid values are specified. Platform-specific fields are identified as such. For all platform-specific configuration values, the scope defined below in the Platform-specific configuration section applies.
ociVersion
(string, REQUIRED) MUST be in SemVer v2.0.0 format and specifies the version of the Open Container Runtime Specification with which the bundle complies. The Open Container Runtime Specification follows semantic versioning and retains forward and backward compatibility within major versions. For example, if a configuration is compliant with version 1.1 of this specification, it is compatible with all runtimes that support any 1.1 or later release of this specification, but is not compatible with a runtime that supports 1.0 and not 1.1.
"ociVersion": "0.1.0"
root
(object, REQUIRED) specifies the container's root filesystem.
-
path
(string, OPTIONAL) Specifies the path to the root filesystem for the container. The path is either an absolute path or a relative path to the bundle. Users SHOULD consider using a conventional name, such asrootfs
.On Windows, for Windows Server Containers, this field is REQUIRED. For Hyper-V Containers, this field MUST be omitted.
On all other platforms, this field is REQUIRED.
On Linux, for example, with a bundle at
/to/bundle
and a root filesystem at/to/bundle/rootfs
, thepath
value can be either/to/bundle/rootfs
orrootfs
.If defined, a directory MUST exist at the path declared by the field.
-
readonly
(bool, OPTIONAL) If true then the root filesystem MUST be read-only inside the container, defaults to false. On Windows, this field must be omitted or false.
"root": {
"path": "rootfs",
"readonly": true
}
mounts
(array of objects, OPTIONAL) specifies additional mounts beyond root
.
The runtime MUST mount entries in the listed order.
For Linux, the parameters are as documented in mount(2) system call man page.
For Solaris, the mount entry corresponds to the 'fs' resource in the zonecfg(1M) man page.
destination
(string, REQUIRED) Destination of mount point: path inside container. This value MUST be an absolute path.- Windows: one mount destination MUST NOT be nested within another mount (e.g., c:\foo and c:\foo\bar).
- Solaris: corresponds to "dir" of the fs resource in zonecfg(1M).
type
(string, OPTIONAL) The type of the filesystem to be mounted.- Linux: filesystem types supported by the kernel as listed in /proc/filesystems (e.g., "minix", "ext2", "ext3", "jfs", "xfs", "reiserfs", "msdos", "proc", "nfs", "iso9660").
- Windows: this field MUST NOT be supplied.
- Solaris: corresponds to "type" of the fs resource in zonecfg(1M).
source
(string, OPTIONAL) A device name, but can also be a directory name or a dummy.- Windows: a local directory on the filesystem of the container host. UNC paths and mapped drives are not supported.
- Solaris: corresponds to "special" of the fs resource in zonecfg(1M).
options
(array of strings, OPTIONAL) Mount options of the filesystem to be used.- Linux: supported options are listed in the mount(8) man page. Note both filesystem-independent and filesystem-specific options are listed.
- Solaris: corresponds to "options" of the fs resource in zonecfg(1M).
"mounts": [
{
"destination": "/tmp",
"type": "tmpfs",
"source": "tmpfs",
"options": ["nosuid","strictatime","mode=755","size=65536k"]
},
{
"destination": "/data",
"type": "bind",
"source": "/volumes/testing",
"options": ["rbind","rw"]
}
]
"mounts": [
{
"destination": "C:\\folder-inside-container",
"source": "C:\\folder-on-host",
"options": []
}
]
"mounts": [
{
"destination": "/opt/local",
"type": "lofs",
"source": "/usr/local",
"options": ["ro","nodevices"]
},
{
"destination": "/opt/sfw",
"type": "lofs",
"source": "/opt/sfw"
}
]
process
(object, OPTIONAL) specifies the container process.
This property is REQUIRED when start
is called.
-
terminal
(bool, OPTIONAL) specifies whether a terminal is attached to that process, defaults to false. As an example, if set to true on Linux a pseudoterminal pair is allocated for the container process and the pseudoterminal slave is duplicated on the container process's standard streams. -
consoleSize
(object, OPTIONAL) specifies the console size in characters of the terminal if attached, containing the following properties:height
(uint, REQUIRED)width
(uint, REQUIRED)
-
cwd
(string, REQUIRED) is the working directory that will be set for the executable. This value MUST be an absolute path. -
env
(array of strings, OPTIONAL) with the same semantics as IEEE Std 1003.1-2001'senviron
. -
args
(array of strings, REQUIRED) with similar semantics to IEEE Std 1003.1-2001execvp
's argv. This specification extends the IEEE standard in that at least one entry is REQUIRED, and that entry is used with the same semantics asexecvp
's file. -
capabilities
(object, OPTIONAL) is an object containing arrays that specifies the sets of capabilities for the process(es) inside the container. Valid values are platform-specific. For example, valid values for Linux are defined in the capabilities(7) man page, such asCAP_CHOWN
. Any value which cannot be mapped to a relevant kernel interface MUST cause an error. capabilities contains the following properties:effective
(array of strings, OPTIONAL) - theeffective
field is an array of effective capabilities that are kept for the process.bounding
(array of strings, OPTIONAL) - thebounding
field is an array of bounding capabilities that are kept for the process.inheritable
(array of strings, OPTIONAL) - theinheritable
field is an array of inheritable capabilities that are kept for the process.permitted
(array of strings, OPTIONAL) - thepermitted
field is an array of permitted capabilities that are kept for the process.ambient
(array of strings, OPTIONAL) - theambient
field is an array of ambient capabilities that are kept for the process.
-
rlimits
(array of objects, OPTIONAL) allows setting resource limits for a process inside the container. Each entry has the following structure:type
(string, REQUIRED) - the platform resource being limited, for example on Linux as defined in the setrlimit(2) man page.soft
(uint64, REQUIRED) - the value of the limit enforced for the corresponding resource.hard
(uint64, REQUIRED) - the ceiling for the soft limit that could be set by an unprivileged process. Only a privileged process (e.g. under Linux: one with the CAP_SYS_RESOURCE capability) can raise a hard limit.
If
rlimits
contains duplicated entries with sametype
, the runtime MUST error out. -
noNewPrivileges
(bool, OPTIONAL) settingnoNewPrivileges
to true prevents the processes in the container from gaining additional privileges. As an example, the 'no_new_privs' article in the kernel documentation has information on how this is achieved using a prctl system call on Linux.
For Linux-based systems the process structure supports the following process-specific fields.
-
apparmorProfile
(string, OPTIONAL) specifies the name of the AppArmor profile to be applied to processes in the container. For more information about AppArmor, see AppArmor documentation. -
oomScoreAdj
(int, OPTIONAL) adjusts the oom-killer score in[pid]/oom_score_adj
for the container process's[pid]
in a [proc pseudo-filesystem][procfs]. IfoomScoreAdj
is set, the runtime MUST setoom_score_adj
to the given value. IfoomScoreAdj
is not set, the runtime MUST NOT change the value ofoom_score_adj
.This is a per-process setting, where as
disableOOMKiller
is scoped for a memory cgroup. For more information on how these two settings work together, see the memory cgroup documentation section 10. OOM Contol. -
selinuxLabel
(string, OPTIONAL) specifies the SELinux label to be applied to the processes in the container. For more information about SELinux, see SELinux documentation.
The user for the process is a platform-specific structure that allows specific control over which user the process runs as.
For Linux and Solaris based systems the user structure has the following fields:
uid
(int, REQUIRED) specifies the user ID in the container namespace.gid
(int, REQUIRED) specifies the group ID in the container namespace.additionalGids
(array of ints, OPTIONAL) specifies additional group IDs (in the container namespace to be added to the process.
Note: symbolic name for uid and gid, such as uname and gname respectively, are left to upper levels to derive (i.e. /etc/passwd
parsing, NSS, etc)
"process": {
"terminal": true,
"consoleSize": {
"height": 25,
"width": 80
},
"user": {
"uid": 1,
"gid": 1,
"additionalGids": [5, 6]
},
"env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"TERM=xterm"
],
"cwd": "/root",
"args": [
"sh"
],
"apparmorProfile": "acme_secure_profile",
"selinuxLabel": "system_u:system_r:svirt_lxc_net_t:s0:c124,c675",
"noNewPrivileges": true,
"capabilities": {
"bounding": [
"CAP_AUDIT_WRITE",
"CAP_KILL",
"CAP_NET_BIND_SERVICE"
],
"permitted": [
"CAP_AUDIT_WRITE",
"CAP_KILL",
"CAP_NET_BIND_SERVICE"
],
"inheritable": [
"CAP_AUDIT_WRITE",
"CAP_KILL",
"CAP_NET_BIND_SERVICE"
],
"effective": [
"CAP_AUDIT_WRITE",
"CAP_KILL"
],
"ambient": [
"CAP_NET_BIND_SERVICE"
]
},
"rlimits": [
{
"type": "RLIMIT_NOFILE",
"hard": 1024,
"soft": 1024
}
]
}
"process": {
"terminal": true,
"consoleSize": {
"height": 25,
"width": 80
},
"user": {
"uid": 1,
"gid": 1,
"additionalGids": [2, 8]
},
"env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"TERM=xterm"
],
"cwd": "/root",
"args": [
"/usr/bin/bash"
]
}
For Windows based systems the user structure has the following fields:
username
(string, OPTIONAL) specifies the user name for the process.
"process": {
"terminal": true,
"user": {
"username": "containeradministrator"
},
"env": [
"VARIABLE=1"
],
"cwd": "c:\\foo",
"args": [
"someapp.exe",
]
}
hostname
(string, OPTIONAL) specifies the container's hostname as seen by processes running inside the container. On Linux, for example, this will change the hostname in the container UTS namespace. Depending on your namespace configuration, the container UTS namespace may be the runtime UTS namespace.
"hostname": "mrsdalloway"
platform
(object, REQUIRED) specifies the configuration's target platform.
os
(string, REQUIRED) specifies the operating system family of the container configuration's specifiedroot
file system bundle. The runtime MUST generate an error if it does not support the specifiedos
. Bundles SHOULD use, and runtimes SHOULD understand,os
entries listed in the Go Language document forGOOS
. If an operating system is not included in theGOOS
documentation, it SHOULD be submitted to this specification for standardization.arch
(string, REQUIRED) specifies the instruction set for which the binaries in the specifiedroot
file system bundle have been compiled. The runtime MUST generate an error if it does not support the specifiedarch
. Values forarch
SHOULD use, and runtimes SHOULD understand,arch
entries listed in the Go Language document forGOARCH
. If an architecture is not included in theGOARCH
documentation, it SHOULD be submitted to this specification for standardization.
"platform": {
"os": "linux",
"arch": "amd64"
}
platform.os
is used to specify platform-specific configuration.
Runtime implementations MAY support any valid values for platform-specific fields as part of this configuration.
linux
(object, OPTIONAL) Linux-specific configuration. This MAY be set ifplatform.os
islinux
and MUST NOT be set otherwise.windows
(object, OPTIONAL) Windows-specific configuration. This MAY be set ifplatform.os
iswindows
and MUST NOT be set otherwise.solaris
(object, OPTIONAL) Solaris-specific configuration. This MAY be set ifplatform.os
issolaris
and MUST NOT be set otherwise.
{
"platform": {
"os": "linux",
"arch": "amd64"
},
"linux": {
"namespaces": [
{
"type": "pid"
}
]
}
}
Hooks allow for the configuration of custom actions related to the lifecycle of the container.
hooks
(object, OPTIONAL) MAY contain any of the following properties:prestart
(array of objects, OPTIONAL) is an array of pre-start hooks. Entries in the array contain the following properties:path
(string, REQUIRED) with similar semantics to IEEE Std 1003.1-2001execv
's path. This specification extends the IEEE standard in thatpath
MUST be absolute.args
(array of strings, OPTIONAL) with the same semantics as IEEE Std 1003.1-2001execv
's argv.env
(array of strings, OPTIONAL) with the same semantics as IEEE Std 1003.1-2001'senviron
.timeout
(int, OPTIONAL) is the number of seconds before aborting the hook. If set,timeout
MUST be greater than zero.
poststart
(array of objects, OPTIONAL) is an array of post-start hooks. Entries in the array have the same schema as pre-start entries.poststop
(array of objects, OPTIONAL) is an array of post-stop hooks. Entries in the array have the same schema as pre-start entries.
Hooks allow users to specify programs to run before or after various lifecycle events. Hooks MUST be called in the listed order. The state of the container MUST be passed to hooks over stdin so that they may do work appropriate to the current state of the container.
The pre-start hooks MUST be called after the start
operation is called but before the user-specified program command is executed.
On Linux, for example, they are called after the container namespaces are created, so they provide an opportunity to customize the container (e.g. the network namespace could be specified in this hook).
The post-start hooks MUST be called after the user-specified process is executed but before the start
operation returns.
For example, this hook can notify the user that the container process is spawned.
The post-stop hooks MUST be called after the container is deleted but before the delete
operation returns.
Cleanup or debugging functions are examples of such a hook.
"hooks": {
"prestart": [
{
"path": "/usr/bin/fix-mounts",
"args": ["fix-mounts", "arg1", "arg2"],
"env": [ "key1=value1"]
},
{
"path": "/usr/bin/setup-network"
}
],
"poststart": [
{
"path": "/usr/bin/notify-start",
"timeout": 5
}
],
"poststop": [
{
"path": "/usr/sbin/cleanup.sh",
"args": ["cleanup.sh", "-f"]
}
]
}
annotations
(object, OPTIONAL) contains arbitrary metadata for the container.
This information MAY be structured or unstructured.
Annotations MUST be a key-value map.
If there are no annotations then this property MAY either be absent or an empty map.
Keys MUST be strings.
Keys MUST be unique within this map.
Keys MUST NOT be an empty string.
Keys SHOULD be named using a reverse domain notation - e.g. com.example.myKey
.
Keys using the org.opencontainers
namespace are reserved and MUST NOT be used by subsequent specifications.
Implementations that are reading/processing this configuration file MUST NOT generate an error if they encounter an unknown annotation key.
Values MUST be strings. Values MAY be an empty string.
"annotations": {
"com.example.gpu-cores": "2"
}
Implementations that are reading/processing this configuration file MUST NOT generate an error if they encounter an unknown property. Instead they MUST ignore unknown properties.
Implementations that are reading/processing this configuration file MUST generate an error when invalid or unsupported values are encountered. Unless support for a valid value is explicitly required, runtimes MAY choose which subset of the valid values it will support.
Here is a full example config.json
for reference.
{
"ociVersion": "0.5.0-dev",
"platform": {
"os": "linux",
"arch": "amd64"
},
"process": {
"terminal": true,
"user": {
"uid": 1,
"gid": 1,
"additionalGids": [
5,
6
]
},
"args": [
"sh"
],
"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"
],
"permitted": [
"CAP_AUDIT_WRITE",
"CAP_KILL",
"CAP_NET_BIND_SERVICE"
],
"inheritable": [
"CAP_AUDIT_WRITE",
"CAP_KILL",
"CAP_NET_BIND_SERVICE"
],
"effective": [
"CAP_AUDIT_WRITE",
"CAP_KILL"
],
"ambient": [
"CAP_NET_BIND_SERVICE"
]
},
"rlimits": [
{
"type": "RLIMIT_CORE",
"hard": 1024,
"soft": 1024
},
{
"type": "RLIMIT_NOFILE",
"hard": 1024,
"soft": 1024
}
],
"apparmorProfile": "acme_secure_profile",
"oomScoreAdj": 100,
"selinuxLabel": "system_u:system_r:svirt_lxc_net_t:s0:c124,c675",
"noNewPrivileges": true
},
"root": {
"path": "rootfs",
"readonly": true
},
"hostname": "slartibartfast",
"mounts": [
{
"destination": "/proc",
"type": "proc",
"source": "proc"
},
{
"destination": "/dev",
"type": "tmpfs",
"source": "tmpfs",
"options": [
"nosuid",
"strictatime",
"mode=755",
"size=65536k"
]
},
{
"destination": "/dev/pts",
"type": "devpts",
"source": "devpts",
"options": [
"nosuid",
"noexec",
"newinstance",
"ptmxmode=0666",
"mode=0620",
"gid=5"
]
},
{
"destination": "/dev/shm",
"type": "tmpfs",
"source": "shm",
"options": [
"nosuid",
"noexec",
"nodev",
"mode=1777",
"size=65536k"
]
},
{
"destination": "/dev/mqueue",
"type": "mqueue",
"source": "mqueue",
"options": [
"nosuid",
"noexec",
"nodev"
]
},
{
"destination": "/sys",
"type": "sysfs",
"source": "sysfs",
"options": [
"nosuid",
"noexec",
"nodev"
]
},
{
"destination": "/sys/fs/cgroup",
"type": "cgroup",
"source": "cgroup",
"options": [
"nosuid",
"noexec",
"nodev",
"relatime",
"ro"
]
}
],
"hooks": {
"prestart": [
{
"path": "/usr/bin/fix-mounts",
"args": [
"fix-mounts",
"arg1",
"arg2"
],
"env": [
"key1=value1"
]
},
{
"path": "/usr/bin/setup-network"
}
],
"poststart": [
{
"path": "/usr/bin/notify-start",
"timeout": 5
}
],
"poststop": [
{
"path": "/usr/sbin/cleanup.sh",
"args": [
"cleanup.sh",
"-f"
]
}
]
},
"linux": {
"devices": [
{
"path": "/dev/fuse",
"type": "c",
"major": 10,
"minor": 229,
"fileMode": 438,
"uid": 0,
"gid": 0
},
{
"path": "/dev/sda",
"type": "b",
"major": 8,
"minor": 0,
"fileMode": 432,
"uid": 0,
"gid": 0
}
],
"uidMappings": [
{
"hostID": 1000,
"containerID": 0,
"size": 32000
}
],
"gidMappings": [
{
"hostID": 1000,
"containerID": 0,
"size": 32000
}
],
"sysctl": {
"net.ipv4.ip_forward": "1",
"net.core.somaxconn": "256"
},
"cgroupsPath": "/myRuntime/myContainer",
"resources": {
"network": {
"classID": 1048577,
"priorities": [
{
"name": "eth0",
"priority": 500
},
{
"name": "eth1",
"priority": 1000
}
]
},
"pids": {
"limit": 32771
},
"hugepageLimits": [
{
"pageSize": "2MB",
"limit": 9223372036854772000
}
],
"memory": {
"limit": 536870912,
"reservation": 536870912,
"swap": 536870912,
"kernel": 0,
"kernelTCP": 0,
"swappiness": 0
},
"cpu": {
"shares": 1024,
"quota": 1000000,
"period": 500000,
"realtimeRuntime": 950000,
"realtimePeriod": 1000000,
"cpus": "2-3",
"mems": "0-7"
},
"disableOOMKiller": false,
"devices": [
{
"allow": false,
"access": "rwm"
},
{
"allow": true,
"type": "c",
"major": 10,
"minor": 229,
"access": "rw"
},
{
"allow": true,
"type": "b",
"major": 8,
"minor": 0,
"access": "r"
}
],
"blockIO": {
"blkioWeight": 10,
"blkioLeafWeight": 10,
"blkioWeightDevice": [
{
"major": 8,
"minor": 0,
"weight": 500,
"leafWeight": 300
},
{
"major": 8,
"minor": 16,
"weight": 500
}
],
"blkioThrottleReadBpsDevice": [
{
"major": 8,
"minor": 0,
"rate": 600
}
],
"blkioThrottleWriteIOPSDevice": [
{
"major": 8,
"minor": 16,
"rate": 300
}
]
}
},
"rootfsPropagation": "slave",
"seccomp": {
"defaultAction": "SCMP_ACT_ALLOW",
"architectures": [
"SCMP_ARCH_X86",
"SCMP_ARCH_X32"
],
"syscalls": [
{
"names": [
"getcwd",
"chmod"
],
"action": "SCMP_ACT_ERRNO"
}
]
},
"namespaces": [
{
"type": "pid"
},
{
"type": "network"
},
{
"type": "ipc"
},
{
"type": "uts"
},
{
"type": "mount"
},
{
"type": "user"
},
{
"type": "cgroup"
}
],
"maskedPaths": [
"/proc/kcore",
"/proc/latency_stats",
"/proc/timer_stats",
"/proc/sched_debug"
],
"readonlyPaths": [
"/proc/asound",
"/proc/bus",
"/proc/fs",
"/proc/irq",
"/proc/sys",
"/proc/sysrq-trigger"
],
"mountLabel": "system_u:object_r:svirt_sandbox_file_t:s0:c715,c811"
},
"annotations": {
"com.example.key1": "value1",
"com.example.key2": "value2"
}
}