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-solaris.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,15 +12,15 @@ The SMF(Service Management Facility) FMRI which should go to "online" state befo
12
12
"milestone": "svc:/milestone/container:default"
13
13
```
14
14
15
-
## <aname="configSolarisLimitpriv" />limitpriv
15
+
## <aname="configSolarisLimitPriv" />limitPriv
16
16
The maximum set of privileges any process in this container can obtain.
17
17
The property should consist of a comma-separated privilege set specification as described in [priv_str_to_set(3C)][priv-str-to-set.3c] man page for the respective release of Solaris.
@@ -80,7 +80,7 @@ The VNIC is deleted when the container is torn down.
80
80
The following properties can be used to set up automatic networks.
81
81
For additional information on properties, check the [zonecfg(1M)][zonecfg.1m_2] man page for the respective release of Solaris.
82
82
83
-
***`linkname`***(string, OPTIONAL)* Specify a name for the automatically created VNIC datalink.
83
+
***`linkName`***(string, OPTIONAL)* Specify a name for the automatically created VNIC datalink.
84
84
***`lowerLink`***(string, OPTIONAL)* Specify the link over which the VNIC will be created.
85
85
Mapped to `lower-link` in the [zonecfg(1M)][zonecfg.1m_2] man page.
86
86
***`allowedAddress`***(string, OPTIONAL)* The set of IP addresses that the container can use might be constrained by specifying the allowedAddress property.
@@ -90,7 +90,7 @@ Mapped to `allowed-address` in the [zonecfg(1M)][zonecfg.1m_2] man page.
90
90
***`configureAllowedAddress`***(string, OPTIONAL)* If configureAllowedAddress is set to true, the addresses specified by allowedAddress are automatically configured on the interface each time the container starts.
91
91
When it is set to false, the allowedAddress will not be configured on container start.
92
92
Mapped to `configure-allowed-address` in the [zonecfg(1M)][zonecfg.1m_2] man page.
93
-
***`defrouter`***(string, OPTIONAL)* The value for the OPTIONAL default router.
93
+
***`defRouter`***(string, OPTIONAL)* The value for the OPTIONAL default router.
94
94
***`macAddress`***(string, OPTIONAL)* Set the VNIC's MAC addresses based on the specified value or keyword.
95
95
If not a keyword, it is interpreted as a unicast MAC address.
96
96
For a list of the supported keywords please refer to the [zonecfg(1M)][zonecfg.1m_2] man page of the respective Solaris release.
@@ -105,16 +105,16 @@ Mapped to `link-protection` in the [zonecfg(1M)][zonecfg.1m_2] man page.
You can indicate that a container should be started in an a mode where disk flushes are not performed during container boot via the OPTIONAL `ignoreflushesduringboot` field of the Windows configuration.
133
+
You can indicate that a container should be started in an a mode where disk flushes are not performed during container boot via the OPTIONAL `ignoreFlushesDuringBoot` field of the Windows configuration.
134
134
135
135
### Example
136
136
137
137
```json
138
138
"windows": {
139
-
"ignoreflushesduringboot": true
139
+
"ignoreFlushesDuringBoot": true
140
140
}
141
141
```
142
142
@@ -146,14 +146,14 @@ You can indicate that a container should be started in an a mode where disk flus
146
146
147
147
The following parameters can be specified:
148
148
149
-
***`utilityvmpath`***(string, OPTIONAL)* - specifies the path to the image used for the utility VM. This would be specified if using a base image which does not contain a utility VM image. If not supplied, the runtime will search the container filesystem layers from the bottom-most layer upwards, until it locates "UtilityVM", and default to that path.
149
+
***`utilityVMPath`***(string, OPTIONAL)* - specifies the path to the image used for the utility VM. This would be specified if using a base image which does not contain a utility VM image. If not supplied, the runtime will search the container filesystem layers from the bottom-most layer upwards, until it locates "UtilityVM", and default to that path.
0 commit comments