This repository has been archived by the owner on May 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 70
pod resources are not honoured in pod config file #925
Comments
devimc
pushed a commit
to devimc/runtime
that referenced
this issue
Jan 15, 2018
VM config resources must be honoured in order to create the pod config with the right number of vCPUs and Memory, whithout this patch vCPU and Memory will be always 0. fixes clearcontainers#925 Signed-off-by: Julio Montes <[email protected]>
devimc
pushed a commit
to devimc/runtime
that referenced
this issue
Jan 15, 2018
VM config resources must be honoured in order to create the pod config with the right number of vCPUs and Memory, whithout this patch vCPU and Memory will be always 0. fixes clearcontainers#925 Signed-off-by: Julio Montes <[email protected]>
I'm seeing the values showing as zero under docker too:
|
@jodh-intel ohh you're right, I forgot to mention that you have to use constrains
|
devimc
pushed a commit
to devimc/runtime
that referenced
this issue
Jan 16, 2018
VM config resources must be honoured in order to create the pod config with the right number of vCPUs and Memory, whithout this patch vCPU and Memory will be always 0. fixes clearcontainers#925 Signed-off-by: Julio Montes <[email protected]>
devimc
pushed a commit
to devimc/runtime
that referenced
this issue
Jan 16, 2018
VM config resources must be honoured in order to create the pod config with the right number of vCPUs and Memory, whithout this patch vCPU and Memory will be always 0. fixes clearcontainers#925 Signed-off-by: Julio Montes <[email protected]>
devimc
pushed a commit
to devimc/runtime
that referenced
this issue
Jan 16, 2018
VM config resources must be honoured in order to create the pod config with the right number of vCPUs and Memory, whithout this patch vCPU and Memory will be always 0. fixes clearcontainers#925 Signed-off-by: Julio Montes <[email protected]>
devimc
pushed a commit
to devimc/runtime
that referenced
this issue
Jan 16, 2018
VM config resources must be honoured in order to create the pod config with the right number of vCPUs and Memory, whithout this patch vCPU and Memory will be always 0. fixes clearcontainers#925 Signed-off-by: Julio Montes <[email protected]>
mcastelino
pushed a commit
to mcastelino/runtime
that referenced
this issue
Dec 6, 2018
…ug-vfio-devices virtcontainers: fix sandbox store struct VFIODevice bug
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description of problem
using constraints, pod vCPus and Memory are always 0 in kubernetes
run a container with kubernetes and take a look to the pod config file
debian.yaml
do the same, but using docker
Expected result
resources should not be 0 in the pod configuration
The text was updated successfully, but these errors were encountered: