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).
@@ -30,6 +31,7 @@ An implementation is compliant for a given CPU architecture if it satisfies all
30
31
Protocols defined by this specification are:
31
32
* Linux containers: [runtime.md](runtime.md), [config.md](config.md), [config-linux.md](config-linux.md), and [runtime-linux.md](runtime-linux.md).
32
33
* Solaris containers: [runtime.md](runtime.md), [config.md](config.md), and [config-solaris.md](config-solaris.md).
34
+
* Windows containers: [runtime.md](runtime.md), [config.md](config.md), and [config-windows.md](config-windows.md).
This document describes the schema for the [Windows-specific section](config.md#platform-specific-configuration) of the [container configuration](config.md).
4
+
The Windows container specification uses APIs provided by the Windows Host Compute Service (HCS) to fulfill the spec.
5
+
6
+
You can configure a container's resource limits via the `resources` field of the Windows configuration.
7
+
Do not specify `resources` unless required.
8
+
9
+
10
+
#### Memory
11
+
12
+
`memory` is an optional configuration for the container's memory usage.
13
+
14
+
The following parameters can be specified:
15
+
16
+
***`limit`***(uint64, optional)* - sets limit of memory usage in bytes
17
+
18
+
***`reservation`***(uint64, optional)* - sets soft limit of memory usage in bytes
19
+
20
+
###### Example
21
+
22
+
```json
23
+
"memory": {
24
+
"limit": 2097152,
25
+
"reservation": 524288
26
+
}
27
+
```
28
+
29
+
#### CPU
30
+
31
+
`cpu` is an optional configuration for the container's CPU usage.
32
+
33
+
The following parameters can be specified:
34
+
35
+
***`count`***(uint64, optional)* - specifies the number of CPUs available to the container.
36
+
37
+
***`shares`***(uint64, optional)* - specifies the relative weight to other containers with CPU shares. The range is from 1 to 10000.
38
+
39
+
***`percent`***(uint, optional)* - specifies the percentage of available CPUs usable by the container.
40
+
41
+
###### Example
42
+
43
+
```json
44
+
"cpu": {
45
+
"percent": 50
46
+
}
47
+
```
48
+
49
+
#### Storage
50
+
51
+
`storage` is an optional configuration for the container's storage usage.
52
+
53
+
The following parameters can be specified:
54
+
55
+
***`iops`***(uint64, optional)* - specifies the maximum Iops for the system drive of the container.
56
+
57
+
***`bps`***(uint64, optional)* - specifies the maximum bytes per second for the system drive of the container.
58
+
59
+
***`sandboxSize`***(uint64, optional)* - specifies the size to expand the system drive of the container to if it is currently smaller.
60
+
61
+
###### Example
62
+
63
+
```json
64
+
"storage": {
65
+
"iops": 50
66
+
}
67
+
```
68
+
69
+
#### Network
70
+
71
+
`network` is an optional configuration for the container's network usage.
72
+
73
+
The following parameters can be specified:
74
+
75
+
***`egressBandwidth`***(uint64, optional)* - specified the maximum egress bandwidth in bytes per second for the container.
0 commit comments