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
Copy file name to clipboardExpand all lines: config-linux.md
-46Lines changed: 0 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,49 +15,3 @@ Valid values are the strings for capabilities defined in [the man page](http://m
15
15
"CAP_NET_BIND_SERVICE"
16
16
]
17
17
```
18
-
19
-
## User namespace mappings
20
-
21
-
```json
22
-
"uidMappings": [
23
-
{
24
-
"hostID": 1000,
25
-
"containerID": 0,
26
-
"size": 10
27
-
}
28
-
],
29
-
"gidMappings": [
30
-
{
31
-
"hostID": 1000,
32
-
"containerID": 0,
33
-
"size": 10
34
-
}
35
-
]
36
-
```
37
-
38
-
uid/gid mappings describe the user namespace mappings from the host to the container.
39
-
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.
40
-
*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.
41
-
There is a limit of 5 mappings which is the Linux kernel hard limit.
42
-
43
-
## Default Devices and File Systems
44
-
45
-
The Linux ABI includes both syscalls and several special file paths.
46
-
Applications expecting a Linux environment will very likely expect these files paths to be setup correctly.
47
-
48
-
The following devices and filesystems MUST be made available in each application's filesystem
Copy file name to clipboardExpand all lines: runtime-config-linux.md
+88Lines changed: 88 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ Each entry has a type field with possible values described below and an optional
9
9
If a path is specified, that particular file is used to join that type of namespace.
10
10
Also, when a path is specified, a runtime MUST assume that the setup for that particular namespace has already been done and error out if the config specifies anything else related to that namespace.
11
11
12
+
*Example*
12
13
```json
13
14
"namespaces": [
14
15
{
@@ -45,6 +46,31 @@ container via system level IPC.
45
46
***user** the container will be able to remap user and group IDs from the host to local users and groups
46
47
within the container.
47
48
49
+
## User namespace mappings
50
+
51
+
uid/gid mappings describe the user namespace mappings from the host to the container.
52
+
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.
53
+
*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.
54
+
There is a limit of 5 mappings which is the Linux kernel hard limit.
55
+
56
+
*Example*
57
+
```json
58
+
"uidMappings": [
59
+
{
60
+
"hostID": 1000,
61
+
"containerID": 0,
62
+
"size": 10
63
+
}
64
+
],
65
+
"gidMappings": [
66
+
{
67
+
"hostID": 1000,
68
+
"containerID": 0,
69
+
"size": 10
70
+
}
71
+
]
72
+
```
73
+
48
74
## Devices
49
75
50
76
Devices is an array specifying the list of devices to be created in the container.
@@ -61,6 +87,20 @@ Next parameters can be specified:
61
87
* uid - uid of device owner
62
88
* gid - gid of device owner
63
89
90
+
Note: The following devices MUST be made available in each Linux application's filesystem
@@ -227,6 +312,7 @@ For more information about SELinux, see [Selinux documentation](http://selinuxp
227
312
Apparmor profile specifies the name of the apparmor profile that will be used for the container.
228
313
For more information about Apparmor, see [Apparmor documentation](https://wiki.ubuntu.com/AppArmor)
229
314
315
+
*Example*
230
316
```json
231
317
"apparmorProfile": "acme_secure_profile"
232
318
```
@@ -238,6 +324,7 @@ Seccomp configuration allows one to configure actions to take for matched syscal
238
324
For more information about Seccomp, see [Seccomp kernel documentation](https://www.kernel.org/doc/Documentation/prctl/seccomp_filter.txt)
239
325
The actions and operators are strings that match the definitions in seccomp.h from [libseccomp](https://github.com/seccomp/libseccomp) and are translated to corresponding values.
240
326
327
+
*Example*
241
328
```json
242
329
"seccomp": {
243
330
"defaultAction": "SCMP_ACT_ALLOW",
@@ -256,6 +343,7 @@ rootfsPropagation sets the rootfs's mount propagation.
256
343
Its value is either slave, private, or shared.
257
344
[The kernel doc](https://www.kernel.org/doc/Documentation/filesystems/sharedsubtree.txt) has more information about mount propagation.
0 commit comments