You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the specifications in the above table of contents, the keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119) (Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997).
@@ -54,11 +56,11 @@ During the `0.x` series of OCI releases we make no backwards compatibility guara
54
56
Development happens on GitHub for the spec.
55
57
Issues are used for bugs and actionable items and longer discussions can happen on the [mailing list](#mailing-list).
56
58
57
-
The specification and code is licensed under the Apache 2.0 license found in the `LICENSE` file of this repository.
59
+
The specification and code is licensed under the Apache 2.0 license found in the [LICENSE](./LICENSE) file.
58
60
59
61
## Code of Conduct
60
62
61
-
Participation in the OpenContainers community is governed by [OpenContainer's Code of Conduct](https://github.com/opencontainers/tob/blob/master/code-of-conduct.md).
63
+
Participation in the OpenContainers community is governed by [OpenContainer's Code of Conduct](https://github.com/opencontainers/tob/blob/d2f9d68c1332870e40693fe077d311e0742bc73d/code-of-conduct.md).
Copy file name to clipboardExpand all lines: ROADMAP.md
-48Lines changed: 0 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,26 +10,6 @@ Listed topics may defer to the [project wiki](https://github.com/opencontainers/
10
10
11
11
## 1.0
12
12
13
-
### Digest and Hashing
14
-
15
-
A bundle is designed to be moved between hosts.
16
-
Although OCI doesn't define a transport method we should have a cryptographic digest of the on-disk bundle that can be used to verify that a bundle is not corrupted and in an expected configuration.
17
-
18
-
*Owner:* philips
19
-
20
-
### Define Container Lifecycle
21
-
22
-
Containers have a lifecycle and being able to identify and document the lifecycle of a container is very helpful for implementations of the spec.
23
-
The lifecycle events of a container also help identify areas to implement hooks that are portable across various implementations and platforms.
24
-
25
-
*Owner:* mrunalp
26
-
27
-
### Define Standard Container Actions (Target release: v0.3.0)
28
-
29
-
Define what type of actions a runtime can perform on a container without imposing hardships on authors of platforms that do not support advanced options.
30
-
31
-
*Owner:* duglin
32
-
33
13
### Container Definition
34
14
35
15
Define what a software container is and its attributes in a cross platform way.
@@ -46,18 +26,6 @@ Proposal: make it an optional feature
46
26
47
27
*Owner:* hqhq (was vishh) robdolinms, bcorrie
48
28
49
-
### Validation Tooling (Target release: v0.3.0)
50
-
51
-
Provide validation tooling for compliance with OCI spec and runtime environment.
52
-
53
-
*Owner:* mrunalp
54
-
55
-
### Testing Framework
56
-
57
-
Provide a testing framework for compliance with OCI spec and runtime environment.
58
-
59
-
*Owner:* liangchenye
60
-
61
29
### Version Schema
62
30
63
31
Decide on a robust versioning schema for the spec as it evolves.
@@ -66,16 +34,6 @@ Resolved but release process could evolve. Resolved for v0.2.0, expect to revisi
66
34
67
35
*Owner:* vbatts
68
36
69
-
### Printable/Compiled Spec
70
-
71
-
Regardless of how the spec is written, ensure that it is easy to read and follow for first time users.
72
-
73
-
Part of this is resolved. Produces an html & pdf.
74
-
Done
75
-
Would be nice to publish to the OCI web site as part of our release process.
76
-
77
-
*Owner:* vbatts
78
-
79
37
### Base Config Compatibility
80
38
81
39
Ensure that the base configuration format is viable for various platforms.
@@ -95,9 +53,3 @@ Ensure that we have lifecycle hooks in the correct places with full coverage ove
95
53
Will probably go away with Vish's work on splitting create and start, and if we have exec.
96
54
97
55
*Owner:*
98
-
99
-
### Distributable Format
100
-
101
-
A common format for serializing and distributing bundles.
Copy file name to clipboardExpand all lines: config-linux.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Linux-specific Container Configuration
2
2
3
+
This document describes the schema for the [Linux-specific section](config.md#platform-specific-configuration) of the [container configuration](config.md).
3
4
The Linux container specification uses various kernel features like namespaces, cgroups, capabilities, LSM, and file system jails to fulfill the spec.
4
-
Additional information is needed for Linux over the [default spec configuration](config.md) in order to configure these various kernel features.
5
5
6
6
## Default File Systems
7
7
@@ -88,7 +88,7 @@ Also, when a path is specified, a runtime MUST assume that the setup for that pa
88
88
```
89
89
90
90
uid/gid mappings describe the user namespace mappings from the host to the container.
91
-
The mappings represent how the bundle `rootfs` expects the user namespace to be setup and the runtime SHOULD NOT modify the permissions on the rootfs to realize the mapping.
91
+
The runtime SHOULD NOT modify the ownership of referenced filesystems to realize the mapping.
92
92
*hostID* is the starting uid/gid on the host to be mapped to *containerID* which is the starting uid/gid in the container and *size* refers to the number of ids to be mapped.
93
93
There is a limit of 5 mappings which is the Linux kernel hard limit.
0 commit comments