-
Notifications
You must be signed in to change notification settings - Fork 543
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Cleanup the spec a bit to remove WG/git text that's not really part o…
…f the spec renamed an href to "container-namespace2" to avoid a dup-warning msg from the PDF generator Signed-off-by: Doug Davis <dug@us.ibm.com>
- Loading branch information
Doug Davis
committed
Nov 16, 2016
1 parent
600b8b4
commit 39af4ce
Showing
6 changed files
with
50 additions
and
53 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,3 @@ | ||
output | ||
schema/validate | ||
code-of-conduct.md | ||
version.md |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# Open Container Initiative Runtime Specification | ||
|
||
The [Open Container Initiative](http://www.opencontainers.org/) develops specifications for standards on Operating System process and application containers. | ||
|
||
Protocols defined by this specification are: | ||
* Linux containers: [runtime.md](runtime.md), [config.md](config.md), [config-linux.md](config-linux.md), and [runtime-linux.md](runtime-linux.md). | ||
* Solaris containers: [runtime.md](runtime.md), [config.md](config.md), and [config-solaris.md](config-solaris.md). | ||
* Windows containers: [runtime.md](runtime.md), [config.md](config.md), and [config-windows.md](config-windows.md). | ||
|
||
# Table of Contents | ||
|
||
- [Introduction](spec.md) | ||
- [Notational Conventions](#notational-conventions) | ||
- [Container Principles](principles.md) | ||
- [Filesystem Bundle](bundle.md) | ||
- [Runtime and Lifecycle](runtime.md) | ||
- [Linux-specific Runtime and Lifecycle](runtime-linux.md) | ||
- [Configuration](config.md) | ||
- [Linux-specific Configuration](config-linux.md) | ||
- [Solaris-specific Configuration](config-solaris.md) | ||
- [Windows-specific Configuration](config-windows.md) | ||
- [Glossary](glossary.md) | ||
|
||
# Notational Conventions | ||
|
||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in [RFC 2119][rfc2119]. | ||
|
||
The key words "unspecified", "undefined", and "implementation-defined" are to be interpreted as described in the [rationale for the C99 standard][c99-unspecified]. | ||
|
||
An implementation is not compliant for a given CPU architecture if it fails to satisfy one or more of the MUST, REQUIRED, or SHALL requirements for the protocols it implements. | ||
An implementation is compliant for a given CPU architecture if it satisfies all the MUST, REQUIRED, and SHALL requirements for the protocols it implements. | ||
|
||
[c99-unspecified]: http://www.open-std.org/jtc1/sc22/wg14/www/C99RationaleV5.10.pdf#page=18 | ||
[rfc2119]: http://tools.ietf.org/html/rfc2119 |