From 0d0d2459818a5626844bc813e75ef5d332b3149a Mon Sep 17 00:00:00 2001 From: Seth Hoenig Date: Mon, 1 Jun 2020 11:16:11 -0500 Subject: [PATCH] docs: reference kernel documentation regarding soft memory limit activation --- website/pages/docs/drivers/docker.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/pages/docs/drivers/docker.mdx b/website/pages/docs/drivers/docker.mdx index a9ad02fe8..f261ba45c 100644 --- a/website/pages/docs/drivers/docker.mdx +++ b/website/pages/docs/drivers/docker.mdx @@ -188,7 +188,8 @@ The `docker` driver supports the following configuration in the job spec. Only parameter of the task resource configuration becomes a soft limit passed to the docker driver as [`--memory_reservation`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory), and `memory_hard_limit` is passed as the [`--memory`](https://docs.docker.com/config/containers/resource_constraints/#limit-a-containers-access-to-memory) - hard limit. + hard limit. When the host is under memory pressure, the behavior of soft limit + activation is governed by the [Kernel](https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt). - `network_aliases` - (Optional) A list of network-scoped aliases, provide a way for a container to be discovered by an alternate name by any other container within