distribution

The official CNCF Distribution image — the open-source container registry that implements the OCI Distribution spec and powers Docker's registry image and many private registries.

distribution, docker registry, container registry, oci, private registry, cncf

What is Distribution?

The Distribution image packages CNCF Distribution, the open-source container registry that implements the OCI Distribution specification and is the engine behind the long-standing Docker registry image. It stores and serves container images and OCI artifacts over HTTP, with pluggable storage backends including the local filesystem, Amazon S3, Google Cloud Storage, and Azure Blob Storage, plus token-based authentication, pull-through caching, and webhook notifications. The image is configured through a config.yml and REGISTRY_* environment variables. It is used by platform teams that run private or air-gapped registries and pull-through caches, and as the foundation of larger registry products.

What is Echo's Distribution image?

Echo's Distribution image is a hardened build of Distribution on Echo's hardened base. Echo images are designed to be a drop-in replacement: swap the image reference in your Dockerfile or deployment manifest and CVEs go to zero without disrupting your config.yml settings, storage backends, authentication, and TLS certificates. 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 Distribution deployments, the distroless variant keeps all runtime operations — image push and pull, manifest and blob storage, garbage collection, and pull-through caching — fully intact while minimizing exposure; the default variant suits platform and infrastructure teams that need shell access for running garbage collection, inspecting the catalog, or debugging authentication.

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

Public Distribution images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a container registry used in production. Distribution images run continuously with access to container images, storage backend credentials, and registry TLS keys. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with the Go runtime dependencies — create exploitable paths that bypass application-layer controls entirely, allowing attackers to move from a network-reachable service to host-level access. For teams running Distribution across many environments, the image is also a steady source of scanner noise in the CI pipeline — every package in the base becomes a finding your security team must triage, even when none of it is reachable from the service. Echo's build retains everything Distribution needs for image push and pull, manifest and blob storage, garbage collection, and pull-through caching while removing the packages that don't belong in a production Distribution container registry. As we covered in our post on how to protect your company from software supply chain attacks, long-running services that hold sensitive data and listen on the network are among the widest attack surfaces in the container stack. 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 images 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 Distribution image with Echo's Distribution image?

Yes. Echo's Distribution image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. config.yml and REGISTRY_* settings, storage drivers, htpasswd or token authentication, TLS certificates, and pull-through cache setups all continue to work without changes to your clients or CI pipelines.

Is Echo's Distribution image FIPS-validated?

Yes. Echo's FIPS-validated images use cryptographic modules with an active FIPS 140-3 CMVP certificate, making them fit for federal use — unlike FIPS-compliant images that haven't been validated. This matters for teams running Distribution workloads inside FedRAMP boundaries, where a container registry that stores and serves the container images every workload in the environment is built from must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Distribution image.

What is Echo's vulnerability management SLA on the Distribution 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 long-running service that holds container images, storage backend credentials, and registry TLS keys and is reachable over the network.

Is Echo's Distribution 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 Distribution deployments, the distroless variant is the leaner, more secure choice; for platform and infrastructure teams that need shell access for running garbage collection, inspecting the catalog, or debugging authentication, the default variant is the right fit.

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

Echo's Distribution image is built from source with only the absolute essentials needed to run the Distribution container registry, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Distribution 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 Distribution 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 platform and infrastructure teams running Distribution under an ATO — whether that's an air-gapped registry, a private artifact store, or a pull-through cache inside an authorization boundary — Echo's hardened Distribution image keeps the container registry layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.

‍

Interested in base images that start and stay clean?