This repository has been archived by the owner on May 6, 2020. It is now read-only.
Support docker run -m MEMORY memory resource constraint/definition
#381
Comments
|
/cc @wcwxyz |
|
+1 This would be very useful to most people (as well as cpu constraint). |
jodh-intel
added a commit
to jodh-intel/runtime
that referenced
this issue
Sep 8, 2017
"docker run -m" is now supported [1], so it no longer needs to be specified in the limitations document. Partially fixes clearcontainers#494. [1] - See containers/virtcontainers#341 and clearcontainers#381. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
mcastelino
pushed a commit
to mcastelino/runtime
that referenced
this issue
Dec 6, 2018
Fix golint ppc64le issues and eventually Travis-CI
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The runtime should support the
docker run -m MEMORYfunctionality.This is most likely tied directly into the .json config and qemu command line setup.
At present there is a fixed size for all containers. It should be flexible on a per-container/VM basis.
Also see:
intel/cc-oci-runtime#805
#380
The text was updated successfully, but these errors were encountered: