erlang 28.5.0.4
Runtime · Language runtime · standard · v28.5.0.4
Hardened Erlang/OTP runtime on the BEAM VM, built for highly concurrent, fault-tolerant systems. Latest stable lines (27/28/29).
Version line
The latest line lives at the base page; older lines have their own page so you can pin and verify exactly that version.
Security report (Trivy)
Security report (Trivy) · erlang 28.5.0.4
Published versions
3 tagsEach tag is a multi-arch index (amd64 + arm64) pinned by digest. Tagged by version, never :latest.
Use it as a base image
Reference it in the FROM line of your Dockerfile. Nonroot, read-only root filesystem, built for amd64 and arm64.
FROM ghcr.io/quenchworks/images/erlang:28.5.0.4Or pull it directly
docker pull ghcr.io/quenchworks/images/erlang:28.5.0.4- Version line
- 28.5.0.4
- Latest line
- 28.5.0.4, 29.0.4, 27.3.4.15
- Architectures
- amd64, arm64
- Runs as
- nonroot (uid 1001)
- Root filesystem
- read-only
- License
- Apache-2.0
Verify the supply chain
This image is cosign-signed and carries an SPDX SBOM and a SLSA build-provenance attestation on the same digest. Check all three before you build on it:
# 1. signature — built and signed by QuenchWorks CI
cosign verify ghcr.io/quenchworks/images/erlang:28.5.0.4 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 2. SLSA build provenance — which workflow built it, from what
cosign verify-attestation --type https://slsa.dev/provenance/v1 ghcr.io/quenchworks/images/erlang:28.5.0.4 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com
# 3. SPDX SBOM — the package inventory
cosign verify-attestation --type https://spdx.dev/Document/v2.3 ghcr.io/quenchworks/images/erlang:28.5.0.4 \
--certificate-identity-regexp 'https://github.com/quenchworks/.+' \
--certificate-oidc-issuer https://token.actions.githubusercontent.comSee the SBOM & provenance guide for reading the SBOM and using these checks in CI.
Best-practice Dockerfile for 28.5.0.4
Assemble a self-contained rebar3 release on the BEAM in the build stage, then copy that release onto a clean erlang base. The release carries the runtime system and only prod deps.
# Build stage: fetch deps and assemble a prod rebar3 release.FROM ghcr.io/quenchworks/images/erlang:28.5.0.4 AS buildUSER rootWORKDIR /appENV REBAR_CACHE_DIR=/tmp/rebar3
COPY rebar.config rebar.lock ./RUN ["rebar3", "get-deps"]COPY . .RUN ["rebar3", "as", "prod", "release"]
# Runtime stage: copy the self-contained release onto a clean erlang base.FROM ghcr.io/quenchworks/images/erlang:28.5.0.4 AS runtimeWORKDIR /appENV HOME=/tmpCOPY --from=build /app/_build/prod/rel/app ./USER 1001EXPOSE 8080CMD ["bin/app", "foreground"]This Dockerfile is pinned to the 28.5.0.4 line. For the line-by-line walkthrough and ecosystem variants (npm/Yarn, pip/uv/Poetry, Maven/Gradle), see the Build hardened imagesguide.
Upstream project: https://www.erlang.org