Skip to content
OCI Runtime Specification
Branch: master
Clone or download
crosbymichael Merge pull request #1007 from KentaTada/Fix-Namespaces-to-use-LinuxNa…

Fix Namespaces to use LinuxNamespaceType
Latest commit 5b71a03 May 7, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tool version: include version in produced docs (#406) May 2, 2016
schema Windows:Have native CommandLine in Process Feb 7, 2019
specs-go Fix Namespaces to use LinuxNamespaceType Apr 19, 2019
.gitattributes README: Document the alternate-week meeting times Mar 23, 2017
.gitignore Cleanup the spec a bit to remove WG/git text that's not really part o… Nov 16, 2016
.mailmap .mailmap: Consolidate James' entries Sep 25, 2017
.pullapprove.yml .pullapprove.yml: Switch to v2 and other project-template updates Jun 5, 2017
.travis.yml Bump Go versions Oct 28, 2018
ChangeLog ChangeLog: Document changes since v1.0.0 Oct 30, 2017 fix typo Mar 30, 2017
LICENSE Add license and DCO information for contributions Jul 2, 2015
MAINTAINERS Remove lk4d4 as maintainer Mar 7, 2017
Makefile .travis: Bump minimum Go version to 1.9 May 9, 2018 updating link to code of conduct in org repository Feb 28, 2019 format specs with 4 spaces indent Jun 1, 2017 bundle: DRYer root.path entry Jun 16, 2017 change new pid namespace description Apr 8, 2019 format specs with 4 spaces indent Jun 1, 2017 config: Add VM-based container configuration section Mar 9, 2018 Update Windows LayerFolder docs Feb 7, 2019 Windows:Have native CommandLine in Process Feb 7, 2019 glossary: Bump JSON spec to RFC 8259 Feb 20, 2018 docs: Added kata-runtime to implementations May 21, 2018
meeting.ics meeting: Bump July meeting from the 4th to the 11th Jun 28, 2018 [Principles] Add anchor tags for headings Dec 1, 2016 make link usage consistent across the specification Mar 3, 2017 runtime-linux: Condition /proc/self/fd symlinks on source existence Mar 16, 2017 fix the link to hook Oct 27, 2017 config: Add VM-based container configuration section Mar 9, 2018 *: Use inline links for remaining internal references May 10, 2017

Open Container Initiative Runtime Specification

The Open Container Initiative develops specifications for standards on Operating System process and application containers.

The specification can be found here.

Table of Contents

Additional documentation about how this group operates:

Use Cases

To provide context for users the following section gives example use cases for each part of the spec.

Application Bundle Builders

Application bundle builders can create a bundle directory that includes all of the files required for launching an application as a container. The bundle contains an OCI configuration file where the builder can specify host-independent details such as which executable to launch and host-specific settings such as mount locations, hook paths, Linux namespaces and cgroups. Because the configuration includes host-specific settings, application bundle directories copied between two hosts may require configuration adjustments.

Hook Developers

Hook developers can extend the functionality of an OCI-compliant runtime by hooking into a container's lifecycle with an external application. Example use cases include sophisticated network configuration, volume garbage collection, etc.

Runtime Developers

Runtime developers can build runtime implementations that run OCI-compliant bundles and container configuration, containing low-level OS and host-specific details, on a particular platform.


Development happens on GitHub for the spec. Issues are used for bugs and actionable items and longer discussions can happen on the mailing list.

The specification and code is licensed under the Apache 2.0 license found in the LICENSE file.

Discuss your design

The project welcomes submissions, but please let everyone know what you are working on.

Before undertaking a nontrivial change to this specification, send mail to the mailing list to discuss what you plan to do. This gives everyone a chance to validate the design, helps prevent duplication of effort, and ensures that the idea fits. It also guarantees that the design is sound before code is written; a GitHub pull-request is not the place for high-level discussions.

Typos and grammatical errors can go straight to a pull-request. When in doubt, start on the mailing-list.


The contributors and maintainers of all OCI projects have monthly meetings, which are usually at 2:00 PM (USA Pacific) on the first Wednesday of every month. There is an iCalendar format for the meetings here. Everyone is welcome to participate via UberConference web or audio-only: +1 415 968 0849 (no PIN needed). An initial agenda will be posted to the mailing list in the week before each meeting, and everyone is welcome to propose additional topics or suggest other agenda alterations there. Minutes are posted to the mailing list and minutes from past calls are archived here, with minutes from especially old meetings (September 2015 and earlier) archived here.

Mailing List

You can subscribe and join the mailing list on Google Groups.


OCI discussion happens on #opencontainers on Freenode (logs).

Git commit

Sign your work

The sign-off is a simple line at the end of the explanation for the patch, which certifies that you wrote it or otherwise have the right to pass it on as an open-source patch. The rules are pretty simple: if you can certify the below (from

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
660 York Street, Suite 102,
San Francisco, CA 94110 USA

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

then you just add a line to every git commit message:

Signed-off-by: Joe Smith <>

using your real name (sorry, no pseudonyms or anonymous contributions.)

You can add the sign off when creating the git commit via git commit -s.

Commit Style

Simple house-keeping for clean git history. Read more on How to Write a Git Commit Message or the Discussion section of git-commit(1).

  1. Separate the subject from body with a blank line
  2. Limit the subject line to 50 characters
  3. Capitalize the subject line
  4. Do not end the subject line with a period
  5. Use the imperative mood in the subject line
  6. Wrap the body at 72 characters
  7. Use the body to explain what and why vs. how
    • If there was important/useful/essential conversation or information, copy or include a reference
  8. When possible, one keyword to scope the change in the subject (i.e. "README: ...", "runtime: ...")
You can’t perform that action at this time.