You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have created a new EKS 1.30 cluster with a gpu instance node group. On the cluster installed from AWS we get an nvidia-device-plugin daemonset and got notified that it is using an EOL Ububntu 16.04 base image.
Which lead me to look at the images for nvcr.io/nvidia/k8s-device-plugin:v0.9.0 and found that the there might be an error with the tag v0.9.0-ubuntu20.04, being actually on the ubuntu16.04 base
Here is a quick check:
docker run -it --platform=linux/amd64 --entrypoint bash nvcr.io/nvidia/k8s-device-plugin:v0.9.0-ubuntu20.04
@yuliyan-valchev-ft it is not clear why you are using such an old devic eplugin image. Are you able to specify the device plugin version? We have just released v0.16.2 and this should be used if possible.
1. Quick Debug Information
2. Issue or feature description
Hello,
We have created a new EKS 1.30 cluster with a gpu instance node group. On the cluster installed from AWS we get an nvidia-device-plugin daemonset and got notified that it is using an EOL Ububntu 16.04 base image.
Which lead me to look at the images for nvcr.io/nvidia/k8s-device-plugin:v0.9.0 and found that the there might be an error with the tag v0.9.0-ubuntu20.04, being actually on the ubuntu16.04 base
Here is a quick check:
docker run -it --platform=linux/amd64 --entrypoint bash nvcr.io/nvidia/k8s-device-plugin:v0.9.0-ubuntu20.04
Maybe the tag needs to be deleted as it is all the same image
The text was updated successfully, but these errors were encountered: