Windows: Add servicing

Signed-off-by: John Howard <jhoward@microsoft.com>
This commit is contained in:
John Howard
2017-05-12 15:04:44 -07:00
parent fae0d09a24
commit 3c0a84ce0e
3 changed files with 22 additions and 1 deletions
+16 -1
View File
@@ -104,4 +104,19 @@ For more information about tooling to generate a gMSA, see [Deployment Overview]
[gMSAOverview]: https://aka.ms/windowscontainers/manage-serviceaccounts
[gMSATooling]: https://aka.ms/windowscontainers/credentialspec-tools
[gMSATooling]: https://aka.ms/windowscontainers/credentialspec-tools
## <a name="configWindowsServicing" />Servicing
When a container terminates, the Host Compute Service indicates if a Windows update servicing operation is pending.
You can indicate that a container should be started in a mode to apply pending servicing operations via the OPTIONAL `servicing` field of the Windows configuration.
### Example
```json
"windows": {
"servicing": true
}
```
+4
View File
@@ -69,6 +69,10 @@
"credentialspec": {
"id": "https://opencontainers.org/schema/bundle/windows/credentialspec",
"type": "object"
},
"servicing": {
"id": "https://opencontainers.org/schema/bundle/windows/servicing",
"type": "boolean"
}
}
}
+2
View File
@@ -434,6 +434,8 @@ type Windows struct {
Resources *WindowsResources `json:"resources,omitempty"`
// CredentialSpec contains a JSON object describing a group Managed Service Account (gMSA) specification.
CredentialSpec interface{} `json:"credentialspec,omitempty"`
// Servicing indicates if the container is being started in a mode to apply a Windows Update servicing operation.
Servicing bool `json:"servicing,omitempty"`
}
// WindowsResources has container runtime resource constraints for containers running on Windows.