docker-fips

What is Docker FIPS?

The Docker image packages the Docker CLI and, in the dind (Docker-in-Docker) variants, the Docker daemon itself, so that CI/CD jobs and automation can build, tag, push, and run containers from inside a container. Docker is the platform that popularized containers, and the official docker image is a staple of pipelines on GitLab CI, Jenkins, Tekton, and similar systems — either as a client that talks to a remote or mounted daemon through the Docker socket, or as a Docker-in-Docker service that provides an isolated daemon for each job. It is used by DevOps and platform teams building and publishing images, by developers running integration tests that need containers, and by operators who need a reproducible, version-pinned Docker client or daemon across pipelines.

The Docker FIPS image is Echo's FIPS variant of Docker: the same container build tooling image, built to run on FIPS 140-3 validated cryptography. It is designed for organizations that sell to or operate for the US government — FedRAMP-authorized services, federal contractors, and regulated industries — where a container build tooling image that builds images and pushes them to registries, often with elevated privileges must use cryptographic modules with an active NIST CMVP certificate, not merely FIPS-enabled libraries.

What is Echo's Docker FIPS image?

Echo's Docker FIPS image is a hardened, FIPS-validated build of Docker on Echo's hardened base. Because Docker is written in Go, its cryptography is handled by a CMVP-validated Go crypto module such as BoringCrypto rather than by OpenSSL; Echo supports OpenSSL, BoringCrypto, and Bouncy Castle across its FIPS images. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest for the docker-fips image and CVEs go to zero without disrupting your Dockerfiles, registry authentication, build arguments, and CI pipeline steps. Every image is tested across clouds, image use cases, and deployment targets. Echo ships every image in two variants:

• Distroless variant — optimized for runtime use, with the smallest possible attack surface
• Default variant — includes essential build tools, package managers, and shells for teams that need operational access

For production Docker deployments, the distroless variant keeps all runtime operations — image builds, registry pushes and pulls, container execution, and daemon operation in dind mode — fully intact while minimizing exposure; the default variant suits DevOps and platform teams that need shell access for debugging builds, inspecting images and layers, or diagnosing registry authentication.

What is the difference between Echo's Docker FIPS image and the public Docker image?

Public Docker images ship on general-purpose bases whose cryptographic libraries have not been validated under FIPS 140-3, and FIPS-enabled is not the same as FIPS-validated — auditors for FedRAMP and other federal frameworks flag the gap. Those bases also include OS-level tooling convenient for development but which contribute CVEs that accumulate on a container build tooling image used in production. Docker images run inside CI pipelines and operational jobs with access to registry credentials, the Docker socket, and source code, and in dind mode runs privileged. OS-level CVEs in the base image — particularly in libraries such as openssl, libc, iptables, and containerd dependencies — create exploitable paths in an environment that application-level controls never see. Because tooling images are pulled and executed constantly across pipelines, they are also a steady source of scanner noise — every package in the base becomes a finding your security team must triage, even when none of it is exercised by the job. Echo's FIPS build retains everything Docker needs for image builds, registry pushes and pulls, container execution, and daemon operation in dind mode while routing cryptography through a validated module and removing the packages that don't belong in a production Docker container build tooling image. As we covered in our post on how to protect your company from software supply chain attacks, build and automation images that run with access to source code, credentials, and deployment targets are a high-value path into everything downstream. Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Echo FIPS images are STIG-hardened, ship with SBOMs in SPDX and CycloneDX formats and signed provenance, and are recognized by all major scanners and mirrored to all major registries, so they fit into existing pipelines without changing your registry, scanner, or runtime tooling.

FAQ

Can I replace my Docker image with Echo's Docker FIPS image?

Yes. Echo's Docker FIPS image is a drop-in replacement. Update the FROM line in your Dockerfile to the docker-fips image and your workloads keep running. Dockerfile builds, registry login and push, Docker socket mounts, TLS settings for the daemon, and dind service definitions all continue to work without changes to your pipelines or Dockerfiles. Because FIPS mode disallows non-approved algorithms, anything that depends on legacy ciphers or hashes such as MD5-based signatures needs to move to approved algorithms.

Is Echo's Docker FIPS image FIPS-validated?

Yes. Echo's FIPS images use CMVP-validated cryptographic modules, operating in a configuration consistent with the module's FIPS 140-3 security policy. Because Docker is written in Go, its cryptography is handled by a CMVP-validated Go crypto module such as BoringCrypto rather than by OpenSSL; Echo supports OpenSSL, BoringCrypto, and Bouncy Castle across its FIPS images. That makes the image fit for federal use — unlike FIPS-enabled or FIPS-compliant images whose cryptographic libraries have never been validated. This matters for teams running Docker inside FedRAMP boundaries, where a container build tooling image that builds images and pushes them to registries, often with elevated privileges must meet cryptographic requirements across the full stack. Echo also provides a FIPS runtime tester that executes approved and unapproved algorithms to show how the image behaves at runtime.

What is Echo's vulnerability management SLA on the Docker FIPS image?

Echo commits to a 7-day SLA for critical and high severity vulnerabilities, and 10 days for medium, low, and unknown — with vulnerabilities triaged within 24 hours. Patches are mirrored automatically into your private registry so you're always running a clean version — critical for a tooling image that is pulled and run constantly across pipelines with access to registry credentials, the Docker socket, and source code, and in dind mode runs privileged.

Is Echo's Docker FIPS image distroless?

Echo ships every image in two variants: a distroless variant optimized for runtime use, and a default variant that includes essential build tools, package managers, and shells. For production Docker deployments, the distroless variant is the leaner, more secure choice; for DevOps and platform teams that need shell access for debugging builds, inspecting images and layers, or diagnosing registry authentication, the default variant is the right fit.

How does Echo achieve such a drastic CVE reduction in Docker?

Echo's Docker FIPS image is built from source with only the absolute essentials needed to run the Docker container build tooling image, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Docker version your applications and their dependencies are certified against — avoiding a disruptive upgrade forced purely by OS-level vulnerabilities in the base image rather than by your own requirements.

Will Echo's Docker FIPS image help us achieve FedRAMP?

Yes. The hard parts of FedRAMP — managing vulnerabilities, applying fixes, and using FIPS-validated cryptography — are baked into Echo images, including STIG-hardened configuration and ConMon/POA&M-ready reporting. For DevOps and platform teams running Docker under an ATO — whether that's container image builds in CI, integration test jobs, or release pipelines publishing to a private registry — Echo's FIPS-validated Docker image keeps the container build tooling image layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍