readystack/otelcol repository overview

⁠OpenTelemetry Collector

readystack/otelcol:v0.164.0-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/otelcol/recipe⁠
• Upstream source at this release's pinned commit (v0.164.0): https://github.com/open-telemetry/opentelemetry-collector-releases/tree/bf626fce5c8053ac6ae9c6c5f4c408c8c182740e⁠
• Product page: https://readystack.dev/products/otelcol⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/otelcol⁠
• Release history (JSON): https://readystack.dev/api/releases/otelcol⁠
• Defect record: https://readystack.dev/defects.html?product=otelcol⁠
• Today's scan: https://readystack.dev/products/otelcol#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=otelcol⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/open-telemetry/opentelemetry-collector-releases v0.164.0 (Apache-2.0), built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Platform and observability teams who collect traces, metrics and logs from many applications and send them to backends.

Why: The OpenTelemetry Collector receives, processes and exports telemetry data in a vendor-agnostic way, so one agent or gateway can replace several separate collectors and agents.

Use case: A team's services emit traces and metrics in different formats, and the team is weighing a new monitoring backend. Every service sends its data to an OpenTelemetry Collector, which processes it and exports it to the current backend and the trial one at the same time, with no change to the services.

About the upstream project, written from its own description: https://github.com/open-telemetry/opentelemetry-collector⁠ · https://opentelemetry.io/docs/collector/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:f56eaf939af6eb2081d5eefa4bfd1607c89a759c006a63767212fa9238630a2b on 2026-10-28.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/otelcol⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:f56eaf939af6eb2081d5eefa4bfd1607c89a759c006a63767212fa9238630a2b; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/otelcol:v0.164.0-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (otelcol).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v0.164.0-CE-ubuntu24.04-r1 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/otelcol:v0.164.0-CE-ubuntu24.04-r1

# ✗ unsupported (do not pull)
docker pull readystack/otelcol:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/otelcol:v0.164.0-CE-ubuntu24.04-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container, single static Go binary (otelcol --config /etc/otelcol/config.yaml) in the foreground. A stateless telemetry pipeline: it receives traces, metrics and logs, processes them and forwards them to the backends you configure. It stores nothing itself: no database, no web UI, no query API.

docker run -d --name otelcol -p 127.0.0.1:4317:4317 -p 127.0.0.1:4318:4318 -p 127.0.0.1:13133:13133 readystack/otelcol:v0.164.0-CE-ubuntu24.04-r1

Starts the collector with the shipped configuration: an OTLP receiver on 4317 (gRPC) and 4318 (HTTP), and a debug exporter that writes one summary line per received batch to the container log. It forwards nothing anywhere until you give it your own configuration with real exporters (see Configuration file in the handbooks). The ports are published on 127.0.0.1 because the OTLP receiver has no authentication (see API authentication in the handbooks); applications in other containers can reach it over a shared Docker network without publishing anything. The archive ships no Compose file.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/otelcol⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:59a91de832a64a1aff37b7303e5053383dda6b83d81776710791b9d4f2d231e4 on 2026-10-27.

— ReadyStack · readystack.dev