From 336d3a43d5a0fe075037cb76b5914d709e95575d Mon Sep 17 00:00:00 2001 From: "James O. D. Hunt" Date: Fri, 8 Sep 2017 08:47:59 +0100 Subject: [PATCH] docs: Remove "docker run -m" from limitations doc "docker run -m" is now supported [1], so it no longer needs to be specified in the limitations document. Partially fixes #494. [1] - See https://github.com/containers/virtcontainers/pull/341 and https://github.com/clearcontainers/runtime/issues/381. Signed-off-by: James O. D. Hunt --- docs/limitations.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/limitations.md b/docs/limitations.md index 4bcfbef4..43d3e28d 100644 --- a/docs/limitations.md +++ b/docs/limitations.md @@ -40,16 +40,6 @@ Due to the way VMs differ in their CPU and memory allocation and sharing across the host system, the implementation of an equivalent method for these commands is potentially challenging. -#### `docker run -m` - -The `docker run -m MEMORY` option is not currently supported. At the -runtime level, this equates to the `linux.resources.memory` OCI -configuration. It should be feasible to pass the relevant information -through to the QEMU `-m` memory size option. This is also related to the -`docker update` command. - -See issue [\#381](https://github.com/clearcontainers/runtime/issues/381) for more information. - #### `docker run --cpus=` The `docker run --cpus=` option is not currently implemented. At the