kubevirt-gpu-device-plugin

packaged by Chainguard

Chainguard Container for kubevirt-gpu-device-plugin

kubevirt-gpu-device-plugin container image that advertises NVIDIA GPUs to kubelet for KubeVirt VMs.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/kubevirt-gpu-device-plugin:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

Chainguard's kubevirt-gpu-device-plugin image is comparable to the upstream image and is designed to be a drop-in replacement for it. It ships the same binary at /usr/bin/nvidia-kubevirt-gpu-device-plugin and the PCI ID database at /usr/pci.ids, and runs as root like the upstream image.

The upstream image starts the plugin through /usr/bin/shelless_ulimit, a wrapper inherited from NVIDIA's distroless base image that sets umask 077 before running the plugin; it raises the open-files limit only when ULIMIT_FLAG=1, which upstream does not set. This image runs the plugin directly with the default umask.

Prerequisites

The plugin advertises NVIDIA GPUs bound to vfio-pci and NVIDIA vGPU mediated devices to the kubelet so that KubeVirt virtual machines can use them. The GPU nodes need IOMMU enabled and their GPUs bound to vfio-pci, or the NVIDIA vGPU host driver. See the upstream documentation for the node setup.

Getting Started

The NVIDIA GPU Operator deploys this plugin as its sandbox device plugin on GPU nodes whose sandbox workload is vm-passthrough or vm-vgpu, set for all nodes by defaultWorkload or per node with the nvidia.com/gpu.workload.config label. Create a values file that points the operator at the Chainguard image:

cat > values.yaml <<EOF
sandboxWorkloads:
  enabled: true
  defaultWorkload: vm-passthrough
sandboxDevicePlugin:
  repository: cgr.dev/ORGANIZATION
  image: kubevirt-gpu-device-plugin
  version: latest
EOF

Then install the GPU Operator with it:

helm repo add nvidia https://helm.ngc.nvidia.com/nvidia
helm repo update
helm install --wait gpu-operator -n gpu-operator --create-namespace \
  nvidia/gpu-operator -f values.yaml

To run the plugin without the operator, use the upstream DaemonSet manifest and set its container image to cgr.dev/ORGANIZATION/kubevirt-gpu-device-plugin:latest. Once the plugin has registered, the GPU nodes advertise one resource per GPU model, for example nvidia.com/GP102GL_TESLA_P40, which KubeVirt virtual machines request by name once the KubeVirt CR permits it: add a spec.configuration.permittedHostDevices.pciHostDevices entry with pciVendorSelector: "10DE:1B38", resourceName: nvidia.com/GP102GL_TESLA_P40, and externalResourceProvider: true. vGPU resources are named per vGPU type instead, for example nvidia.com/GRID_T4-1Q, and need a permittedHostDevices.mediatedDevices entry with mdevNameSelector: "GRID T4-1Q", resourceName: nvidia.com/GRID_T4-1Q, and externalResourceProvider: true.

Documentation and Resources

• KubeVirt GPU Device Plugin
• GPU Operator with KubeVirt
• KubeVirt host devices and GPUs

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.