Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker image tag v0.9.0-ubuntu20.04 #833

Open
yuliyan-valchev-ft opened this issue Jul 17, 2024 · 3 comments
Open

Docker image tag v0.9.0-ubuntu20.04 #833

yuliyan-valchev-ft opened this issue Jul 17, 2024 · 3 comments

Comments

@yuliyan-valchev-ft
Copy link

yuliyan-valchev-ft commented Jul 17, 2024

1. Quick Debug Information

  • OS/Version(e.g. RHEL8.6, Ubuntu22.04):
  • Kernel Version:
  • Container Runtime Type/Containerd
  • K8s Flavor/EKS 1.30

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

root@76e879e636b3:/# cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.7 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.7 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Maybe the tag needs to be deleted as it is all the same image

image
@elezar
Copy link
Member

elezar commented Aug 8, 2024

@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.

@elezar
Copy link
Member

elezar commented Aug 8, 2024

It seems as if the EKS documentation here is out of date.

Screenshot 2024-08-08 at 16 32 25

Our recommended mechanism for installing and managing the plugin is Helm. The instructions from the README should be ablicable to EKS too.

@vara-bonthu
Copy link

We are working on updating these docs. Will update the issue once it's resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants