dhi.io/multus-cni
Multus CNI
Multus CNI is a CNI meta-plugin that enables attaching multiple network interfaces to Kubernetes pods
pushed 16 hours ago
linux/amd64, linux/arm64
64.61 MB
for linux/amd64
80
for linux/amd64
Active support
multus, multus-daemon, multus-shim, install_multus, thin_entrypoint, kubeconfig_generator, cert-approver, passthru
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 Multus CNI
Multus CNI is a Container Network Interface (CNI) meta-plugin for Kubernetes that enables attaching multiple network interfaces to a pod. By default, a Kubernetes pod has a single network interface (in addition to loopback); Multus acts as a meta-plugin that calls other CNI plugins to attach additional interfaces, enabling multi-homed pods for use cases such as network function virtualization (NFV) and telco workloads that require separate control, management, and data plane networks.
Multus CNI follows the Kubernetes Network Custom Resource Definition De-facto Standard put forward by the Kubernetes Network Plumbing Working Group (NPWG), and can be deployed in either a lightweight "thin plugin" mode or a client/server "thick plugin" mode that adds features such as metrics.
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
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.