dhi.io/docker-dind
Docker dind
Docker-in-Docker (dind) runs a full Docker Engine inside a container so you can build and run containers within a container, for CI pipelines and nested workloads.
pushed 2 days ago
linux/amd64, linux/arm64
102.13 MB
for linux/amd64
578
for linux/amd64
Active support
Docker Engine, Docker CLI, Docker Buildx, containerd, runc
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 Docker dind
Docker dind (Docker-in-Docker) runs a full Docker Engine, dockerd, inside a container so that Docker CLI clients can
build and run nested containers without accessing the host's Docker socket. It's commonly used for CI/CD pipelines,
testcontainers, and other automation that needs an isolated Docker daemon per job or per test run. The image ships
dockerd, the docker CLI, docker buildx, containerd, and runc, and generates TLS certificates automatically at
startup so clients can connect securely over the network.
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
Docker and the Docker logo are trademarks or registered trademarks of Docker, Inc. Any use by Docker of other companies' trademarks, product names, or logos are for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.