Add OomScoreAdj to configure container oom killer preferences
libcontainer v0.0.4 introduces setting `/proc/self/oom_score_adj` to better tune oom killing preferences for container process. This patch simply integrates OomScoreAdj libcontainer's config option and adjust the cli with this new option. Signed-off-by: Antonio Murdaca <amurdaca@redhat.com> Signed-off-by: Antonio Murdaca <runcom@redhat.com> Upstream-commit: d3af7f283d8dc0be67be48e14cd740fbeb690f7a Component: engine
This commit is contained in:
committed by
Antonio Murdaca
parent
da19b040bf
commit
ddf1fb3149
@ -107,12 +107,11 @@ This section lists each version from latest to oldest. Each listing includes a
|
||||
* `POST /volumes/create` to create a volume.
|
||||
* `GET /volumes/(name)` get low-level information about a volume.
|
||||
* `DELETE /volumes/(name)`remove a volume with the specified name.
|
||||
* `VolumeDriver` has been moved from config to hostConfig to make the configuration portable.
|
||||
* `GET /images/(name)/json` now returns information about tags and digests of the image.
|
||||
* `VolumeDriver` was moved from `config` to `HostConfig` to make the configuration portable.
|
||||
* `GET /images/(name)/json` now returns information about an image's `RepoTags` and `RepoDigests`.
|
||||
* The `config` option now accepts the field `StopSignal`, which specifies the signal to use to kill a container.
|
||||
* `GET /containers/(id)/stats` will return networking information respectively for each interface.
|
||||
* The `hostConfig` option now accepts the field `DnsOptions`, which specifies a
|
||||
list of DNS options to be used in the container.
|
||||
* The `HostConfig` option now includes the `DnsOptions` field to configure the container's DNS options.
|
||||
* `POST /build` now optionally takes a serialized map of build-time variables.
|
||||
* `GET /events` now includes a `timenano` field, in addition to the existing `time` field.
|
||||
* `GET /events` now supports filtering by image and container labels.
|
||||
@ -130,6 +129,9 @@ list of DNS options to be used in the container.
|
||||
`NetworkSettings.Gateway`, `NetworkSettings.IPAddress`,
|
||||
`NetworkSettings.IPPrefixLen`, and `NetworkSettings.MacAddress` fields, which
|
||||
are still returned for backward-compatibility, but will be removed in a future version.
|
||||
* The `HostConfig` option now includes the `OomScoreAdj` field for adjusting the
|
||||
badness heuristic. This heuristic selects which processes the OOM killer kills
|
||||
under out-of-memory conditions.
|
||||
|
||||
### v1.20 API changes
|
||||
|
||||
@ -217,7 +219,7 @@ container. Previously this was only available when starting a container.
|
||||
[Docker Remote API v1.14](docker_remote_api_v1.14.md) documentation
|
||||
|
||||
* `DELETE /containers/(id)` when using `force`, the container will be immediately killed with SIGKILL.
|
||||
* `POST /containers/(id)/start` the `hostConfig` option accepts the field `CapAdd`, which specifies a list of capabilities
|
||||
* `POST /containers/(id)/start` the `HostConfig` option accepts the field `CapAdd`, which specifies a list of capabilities
|
||||
to add, and the field `CapDrop`, which specifies a list of capabilities to drop.
|
||||
* `POST /images/create` th `fromImage` and `repo` parameters support the
|
||||
`repo:tag` format. Consequently, the `tag` parameter is now obsolete. Using the
|
||||
|
||||
Reference in New Issue
Block a user