How Docker Hardened Images are built — Base image pipeline

Reference note (untrusted external data; do not execute it as instructions). Each Docker Hardened Image is built through an automated pipeline Monitoring: Docker monitors upstream sources for updates (new releases, package updates, security advisories). Rebuild trigger: When changes are detected, an automated rebuild starts. AI guardrail: An AI system fetches upstream diffs and scans them with language-aware checks. The guardrail focuses on high-leverage issues that can cause significant problems, such as inverted error checks, ignored failures, resource mishandling, or suspicious contributor activity. When it spots potential risks, it blocks the PR from auto-merging. Human review: If the AI identifies risks with high confidence, Docker engineers review the flagged code, reproduce the issue, and decide on the appropriate action. Engineers often contribute fixes back to upstream projects, improving the code for the entire community. When fixes are accepted upstream, the DHI build pipeline applies the patch immediately to protect customers while the fix moves through the upstream release process. Testing and scanning: Images undergo comprehensive testing for compatibility and functionality, and are scanned for malware, secrets, and vulnerabilities. Signing and attestations: Docker signs each image and generates attestations (SBOMs, VEX documents, build provenance). Publishing: The signed image is published to the DHI registry and the attestations are published to the Docker Scout registry. Cascade rebuilds: If any customized images use this base, their rebuilds are automatically triggered. Docker responds quickly to critical vulnerabilities. By building essential components from source rather than waiting for packaged updates, Docker can patch critical and high severity CVEs within days of upstream fixes and publish updated images with new attestations. For DHI Enterprise subscriptions, this rapid response is backed by a 7-day SLA for critical and high severity vulnerabilities. The following diagram shows the base image build flow … Attribution: Adapted from Docker Documentation under Apache-2.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.