Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Commit

Permalink
docs: Remove "docker run -m" from limitations doc
Browse files Browse the repository at this point in the history
"docker run -m" is now supported [1], so it no longer needs to be
specified in the limitations document.

Partially fixes #494.

[1] - See containers/virtcontainers#341 and
#381.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
  • Loading branch information
jodh-intel committed Sep 8, 2017
1 parent aa5993d commit 336d3a4
Showing 1 changed file with 0 additions and 10 deletions.
10 changes: 0 additions & 10 deletions docs/limitations.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 336d3a4

Please # to comment.