dhi.io/jaeger-es-rollover
Jaeger ES Rollover
Jaeger es-rollover initializes, rolls over and trims the aliased Jaeger indices in an Elasticsearch cluster.
pushed 22 hours ago
linux/amd64, linux/arm64
15.76 MB
for linux/amd64
79
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 ES Rollover
Jaeger is an open-source, end-to-end distributed tracing platform used to monitor and
troubleshoot transactions in complex microservice architectures. When Jaeger stores spans in Elasticsearch it can write
through read and write aliases instead of one index per day, so that indices roll over by age, size or document count.
This image ships the Jaeger es-rollover tool, which prepares Elasticsearch for that mode and keeps it running: init
creates the index templates, the first numbered index and the aliases; rollover moves the write alias to a new index
when the configured conditions are met; lookback drops indices older than a window from the read alias. Each
subcommand runs to completion and exits, so init is run once and the other two are scheduled as recurring jobs.
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.