AliyunContainerService/gpushare-device-plugin

Issues

• containerd and nvidia-container-runtime instead of nvidia-docker2

  #51 opened 3 years ago by Frank-17
  2

• ALIYUN_COM_GPU_MEM_IDX in the annotation is different than ALIYUN_COM_GPU_MEM_IDX inside the pod

  #61 opened a year ago by wokalski
  1

• How to guarantee the pod does not use more memory than allocation?

  #24 opened 5 years ago by hyc3z
  1

• Can it take effect on the window node?

  #60 opened a year ago by RowgerGo
  0

• 节点有多个不同型号GPU(显存也不一致)时会以第一个识别到的GPU为准

  #59 opened 2 years ago by SakuraAxy
  0

• ResourceExhausted desc = grpc: received message larger than max (4986010 vs. 4194304)

  #57 opened 2 years ago by k0nstantinv
  0

• trivy image scan lists critical and high vulnerability against latest image k8s-gpushare-plugin:v2-1.11-aff8a23

  #56 opened 2 years ago by carlwang87
  0

• NVIDIA_VISIBLE_DEVICES wrong value in OCI spec

  #55 opened 2 years ago by k0nstantinv
  0

• 该程序在 k8s .1.25中无法使用

  #54 opened 2 years ago by blankxyz
  0

• No Devices found. Waiting indefinitely.

  #49 opened 3 years ago by clennpillo
  1

• nvidia-container-cli: device error: unknown device id: no-gpu-has-256MiB-to-run\\\\n\\\"\"": unknown

  #23 opened 5 years ago by zhaogaolong
  3

• question about pods with multiple containers

  #12 opened 6 years ago by monstercy
  3

• [问题] Device Plugin allocate 选出的 pod 是否会跟 Kubelet 绑定的不一致

  #16 opened 5 years ago by orainxiong
  4

• support for vgl

  #52 opened 3 years ago by umberto10
  0

• 插件能获取GPU的个数，但是获取不了GPU的显存，共享无法调度

  #47 opened 3 years ago by gxwangit
  2

• Question: request gpushare on the same GPU

  #43 opened 3 years ago by xhejtman
  3

• How to install on Mac?

  #45 opened 3 years ago by 2811299
  0

• 集群内pod数量过多的情况有可能会引起集群高负载从而雪崩，另外MiB单位有可能会引起kubelet grpc单位失败

  #39 opened 3 years ago by qmloong
  0

• PLEASE GIVE US A BINARY

  #37 opened 4 years ago by mariusehr1
  0

• GPU device not detected with nvidia driver > 430.XX

  #36 opened 4 years ago by ptonelli
  1

• 节点重启后，发现gpu显存超分了

  #35 opened 4 years ago by zlingqu
  0

• Unable to schedule pod with: Insufficient aliyun.com/gpu-mem

  #28 opened 4 years ago by k0nstantinv
  1

• GPU registered to Kubelet but not available in `kubectl inspect gpushare` and not schedulable when using --memory-unit=Mib

  #30 opened 4 years ago by dontmint
  0

• Allocate 中getCandidatePods是否多此一举？

  #29 opened 4 years ago by malixian
  0

• kubectl-inspect-gpushare: fatal with OpenID as auth-provider

  #27 opened 4 years ago by k0nstantinv
  0

• Concurrently create sharegpu instance will cause creation to fail

  #26 opened 5 years ago by guunergooner
  0

• some problem about auto allocate GPU card

  #25 opened 5 years ago by guobingithub
  1

• No assume timestamp for pod tf-jupyter-... so it's not GPUSharedAssumed assumed pod.

  #19 opened 5 years ago by jear
  2

• How to guarantee the pod to be running after Allocate?

  #4 opened 6 years ago by wjliu
  5

• device plugin failed to detect gpu info correctly

  #17 opened 5 years ago by pan87232494
  7

• device login fail to register

  #6 opened 6 years ago by tjliupeng
  1

• Can't pull your docker image

  #11 opened 6 years ago by morecoffee101
  1

• Failed due to invalid configuration: no server found for cluster "local"

  #7 opened 6 years ago by ZhengRongTan
  4

• `aliyun.com/gpu-mem` when did you update to nodestatus

  #2 opened 6 years ago by angao
  1

• device plugin allocate judge error

  #1 opened 6 years ago by angao
  3