dhi.io/jaeger-ingester
Jaeger Ingester
Jaeger v2 unified binary preconfigured to ingest spans from Kafka into a storage backend.
pushed 7 hours ago
linux/amd64, linux/arm64
32.37 MB
for linux/amd64
351
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Jaeger Ingester
Jaeger is an open-source, end-to-end distributed tracing platform used to monitor and
troubleshoot transactions in complex microservice architectures. In Jaeger v2, the separate per-component binaries from
v1 (collector, query, ingester) were unified into a single OpenTelemetry Collector-based jaeger binary. This image
ships that unified binary preconfigured to run in Kafka-ingester mode: it consumes spans from a Kafka topic and writes
them to a configured storage backend, fulfilling the role of the storage-side consumer in a
jaeger-collector → Kafka → jaeger-ingester → storage pipeline.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
Jaeger is a trademark of The Linux Foundation. All rights in the mark are reserved to The Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.