dhi.io/kai-gpu-fractioning-mpsd
KAI GPU Fractioning MPS Daemon
Runs and supervises the NVIDIA MPS control daemon with GPU memory accounting on each GPU node.
pushed 11 hours ago
linux/amd64, linux/arm64
38.40 MB
for linux/amd64
146
for linux/amd64
Active support
-
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.
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.
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.
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.
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.
-
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About KAI GPU Fractioning MPS Daemon
GPU Fractioning lets multiple pods share a single GPU with enforced memory boundaries. mpsd runs and supervises the NVIDIA MPS control daemon on each GPU node with per-process GPU memory accounting enabled, restarting it if it stops, and labels the node with the NVIDIA driver major version it reads through NVML.
The NVIDIA container runtime injects the host driver's NVML library and the MPS control binary into the container, so the image carries neither. The operator runs mpsd as a DaemonSet on the GPU nodes.
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 trademark and/or registered trademark of NVIDIA Corporation. Kubernetes® is a registered trademark of 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 other 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.