From 6ba6265d1ad86680ad7f7750ae1f9abb72f1e728 Mon Sep 17 00:00:00 2001 From: Justin Cormack Date: Fri, 15 Jul 2016 14:11:54 +0100 Subject: [PATCH] Document --oom-score-adj flag in docker run This was only mentioned in docker create documentation. Signed-off-by: Justin Cormack --- docs/reference/run.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/reference/run.md b/docs/reference/run.md index 15d75a0155..ae40cf4bc7 100644 --- a/docs/reference/run.md +++ b/docs/reference/run.md @@ -698,6 +698,7 @@ container: | `--device-read-iops="" ` | Limit read rate (IO per second) from a device (format: `:`). Number is a positive integer. | | `--device-write-iops="" ` | Limit write rate (IO per second) to a device (format: `:`). Number is a positive integer. | | `--oom-kill-disable=false` | Whether to disable OOM Killer for the container or not. | +| `--oom-score-adj=0` | Tune container's OOM preferences (-1000 to 1000) | | `--memory-swappiness=""` | Tune a container's memory swappiness behavior. Accepts an integer between 0 and 100. | | `--shm-size=""` | Size of `/dev/shm`. The format is ``. `number` must be greater than `0`. Unit is optional and can be `b` (bytes), `k` (kilobytes), `m` (megabytes), or `g` (gigabytes). If you omit the unit, the system uses bytes. If you omit the size entirely, the system uses `64m`. | @@ -830,7 +831,10 @@ The following example, illustrates a dangerous way to use the flag: $ docker run -it --oom-kill-disable ubuntu:14.04 /bin/bash The container has unlimited memory which can cause the host to run out memory -and require killing system processes to free memory. +and require killing system processes to free memory. The `--oom-score-adj` +parameter can be changed to select the priority of which containers will +be killed when the system is out of memory, with negative scores making them +less likely to be killed an positive more likely. ### Kernel memory constraints