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

Update limitations doc #494

Closed
jodh-intel opened this issue Aug 31, 2017 · 0 comments
Closed

Update limitations doc #494

jodh-intel opened this issue Aug 31, 2017 · 0 comments
Assignees

Comments

@jodh-intel
Copy link
Contributor

This is now slightly out-of-date:

As a minimum, it needs to be updated for:

  • docker run -m (supported)
  • docker run --cpu-quota + docker run --cpu-period
    (supported, so relates to docker run --cpus).
jodh-intel added a commit to jodh-intel/runtime that referenced this issue Sep 8, 2017
Mention that although `--cpus` is not supported, `--cpu-quota` and `--cpu-period` are [1].

Fixes clearcontainers#494.

[1] - See containers/virtcontainers#344 and
clearcontainers#436.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel added a commit to jodh-intel/runtime that referenced this issue Sep 8, 2017
Mention that although `--cpus` is not supported, `--cpu-quota` and `--cpu-period` are [1].

Fixes clearcontainers#494.

[1] - See containers/virtcontainers#344 and
clearcontainers#436.

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
It helps tracking each request that is sent and we can match with the
one printed by kata-agent on the guest side to find out any stack
requests in the middle.

Fixes: clearcontainers#494

Signed-off-by: Peng Tao <bergwolf@gmail.com>
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants