dhi.io/node-problem-detector
Node Problem Detector
A Kubernetes daemon that detects node-level problems — kernel issues, hardware faults, and runtime failures — and reports them to the API server as Events and NodeConditions.
pushed 2 days ago
linux/amd64, linux/arm64
32.97 MB
for linux/amd64
152
for linux/amd64
Active support
node-problem-detector, health-checker, log-counter
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 Node Problem Detector
Node Problem Detector is a Kubernetes daemon that runs on each node — typically as a DaemonSet — to detect node-level
problems such as kernel deadlocks, corrupted file systems, unresponsive container runtimes, and hardware faults, and
report them to the API server as Events and NodeConditions. This image is built with journald support enabled and ships
the node-problem-detector daemon along with the health-checker and log-counter helper binaries.
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
Kubernetes and the Kubernetes logo are registered trademarks 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.