erlang
The official Erlang image — the Erlang/OTP runtime and build tools for fault-tolerant, highly concurrent, soft real-time systems such as messaging, telecom, and distributed backends.
What is Erlang?
The Erlang image packages Erlang/OTP, the language, virtual machine (BEAM), and libraries built for massively concurrent, distributed, and fault-tolerant systems. Erlang powers telecom switches, messaging platforms, and databases such as RabbitMQ and CouchDB, and the official image includes the Erlang runtime, the erl shell and compiler, and typically rebar3 for builds. It is commonly used in the build stage of multi-stage Dockerfiles for Erlang and Elixir releases, as a runtime for OTP releases, and for development containers. It is used by backend and platform teams that run Erlang-based services.
What is Echo's Erlang image?
Echo's Erlang image is a hardened build of Erlang 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 OTP releases, rebar3 builds, vm.args settings, and Erlang distribution configuration. 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 Erlang deployments, the distroless variant keeps all runtime operations — BEAM execution, process scheduling, OTP application startup, and node clustering — fully intact while minimizing exposure; the default variant suits application and platform teams that need shell access for running the Erlang shell, compiling with rebar3, or attaching to a running node.
What is the difference between Echo's Erlang image and the public Erlang image?
Public Erlang images ship on bases that include OS-level tooling convenient for development but which contribute CVEs that accumulate on a language runtime used in production. Erlang images run with access to your application code, dependencies, and the environment variables and credentials your orchestrator injects. OS-level CVEs in the base image — particularly in libraries such as openssl, zlib, and libc, along with ncurses and the BEAM runtime dependencies — create exploitable paths that bypass application-layer controls entirely. For teams running many services, the image is also one of the largest sources 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 application. Echo's build retains everything Erlang needs for BEAM execution, process scheduling, OTP application startup, and node clustering while removing the packages that don't belong in a production Erlang language runtime. As we covered in our post on how to protect your company from software supply chain attacks, runtime and build images that combine access to source code, secrets, and network exposure 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 Erlang image with Echo's Erlang image?
Yes. Echo's Erlang image is a drop-in replacement. Update the FROM line in your Dockerfile and your workloads keep running. rebar3 builds, OTP releases, vm.args and sys.config files, and node clustering with Erlang cookies all continue to work without changes to your application code or releases.
Is Echo's Erlang 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 Erlang workloads inside FedRAMP boundaries, where a language runtime that runs OTP applications that handle concurrent connections and exchange messages across clustered nodes must meet cryptographic requirements across the full stack — including the OpenSSL and TLS libraries bundled with the Erlang image.
What is Echo's vulnerability management SLA on the Erlang 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 language runtime that runs with access to your code, dependencies, and injected secrets.
Is Echo's Erlang 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 Erlang deployments, the distroless variant is the leaner, more secure choice; for application and platform teams that need shell access for running the Erlang shell, compiling with rebar3, or attaching to a running node, the default variant is the right fit.
How does Echo achieve such a drastic CVE reduction in Erlang?
Echo's Erlang image is built from source with only the absolute essentials needed to run the Erlang language runtime, which significantly shrinks the attack surface. Echo also patches aggressively over time, with backports available so you can stay on the Erlang 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 Erlang 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 application and platform teams running Erlang under an ATO — whether that's a messaging backbone, a telecom-grade service, or a distributed backend — Echo's hardened Erlang image keeps the language runtime layer in-boundary and compliant without requiring custom hardening scripts or manual base image patching between compliance cycles.
.avif)