Sign inSign up
NVIDIA k8s-cc-manager

dhi.io/k8s-cc-manager

NVIDIA k8s-cc-manager

CIS
linux/amd64
linux/arm64

NVIDIA manager for enabling GPU Confidential Computing and Protected PCIe modes from Kubernetes node labels.

Image

pushed 5 hours ago

View image detail
Platforms

linux/amd64, linux/arm64

Size

41.85 MB

for linux/amd64

Packages

139

for linux/amd64

Support

Active support

Tools included

k8s-cc-manager, gpu-admin-tools

What's includedWhy it matters
SLSA Provenance

Build Level 3

Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.

SBOM

CycloneDX SBOM + SPDX SBOM

A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.

VEX

A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.

DHI Image Sources

Available

A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.

CVEs
0
0
1
1
1

Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.

Changelog

Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.

Secrets scan

Verifies no keys, tokens, or credentials were accidentally baked into the image.

Virus scan

The image layers were scanned for known malware signatures before publishing.


About NVIDIA k8s-cc-manager

NVIDIA k8s-cc-manager is a Kubernetes component that enables and manages GPU Confidential Computing (CC) mode, and Protected PCIe (PPCIe) multi-GPU mode, on supported NVIDIA GPUs. It runs as a DaemonSet on GPU nodes and watches the nvidia.com/cc.mode node label. When the label changes, it optionally evicts NVIDIA GPU Operator components, applies the requested mode directly against the GPU hardware, and reschedules the operator components. It reports progress back to the node through the nvidia.com/cc.mode.state and nvidia.com/cc.ready.state labels.

This is the Python implementation of the manager. It uses the official Kubernetes Python client to watch node labels and the vendored NVIDIA gpu-admin-tools library to query and set CC/PPCIe mode and to reset GPUs over PCI. Because it pokes GPU PCI registers and resets devices, the container must run as root and privileged, with host /sys and /dev mounted.

About Docker Hardened Images

Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.

Why use Docker Hardened Images?

These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.

Trademarks

NVIDIA® is a registered trademark of NVIDIA Corporation. All rights in the mark are reserved to NVIDIA Corporation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.

Kubernetes® is a trademark of the Linux Foundation. All rights in the mark are reserved to the Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.

This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.