dhi.io/amazon-k8s-cni-init
amazon-k8s-cni-init
Init container for AWS VPC CNI that copies CNI artifacts to the host and performs initial node network configuration.
pushed 22 hours ago
linux/amd64, linux/arm64
65.65 MB
for linux/amd64
142
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 amazon-vpc-cni-k8s (init container)
Init container for the Amazon VPC CNI plugin. It runs once per node to copy CNI binaries and supporting artifacts into
the host CNI directory and perform the node-level setup the main aws-node container relies on.
Use this image as the aws-vpc-cni-init init container alongside the Docker Hardened amazon-k8s-cni image in the same
DaemonSet, following upstream Amazon VPC CNI manifests or Helm values.
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
Amazon Web Services, AWS, and Amazon EFS are trademarks or registered trademarks of Amazon.com, Inc. or its affiliates. All rights in the marks are reserved to Amazon.com, Inc. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.