victoriatraces

packaged by Chainguard

Chainguard Container for victoriatraces

Fast, cost-effective image for VictoriaTraces, a distributed tracing span database with OpenTelemetry ingestion and Jaeger/Tempo query APIs, built on the VictoriaLogs engine.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/victoriatraces:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This image is built from the VictoriaTraces source and cgr.dev/ORGANIZATION/victoriatraces is a drop-in replacement for victoriametrics/victoria-traces:latest.

The image preserves the upstream entrypoint (/victoria-traces-prod) and / working directory. It runs as UID and GID 65532 instead of root, so mounted host paths must grant that user write access to /victoria-traces-data. The HTTP API and the built-in vmui web UI are served on port 10428.

Getting Started

Running with Docker

docker run -d --name victoriatraces \
  -v victoriatraces-data:/victoria-traces-data \
  -p 10428:10428 \
  cgr.dev/ORGANIZATION/victoriatraces:latest \
  -storageDataPath=/victoria-traces-data

Once it is running, open the built-in web UI at http://localhost:10428/select/vmui/.

Deploying with Helm

Create a values file for the official Helm chart:

cat > values.yaml <<'EOF'
server:
  image:
    registry: cgr.dev
    repository: ORGANIZATION/victoriatraces
    tag: latest
EOF

helm install victoriatraces victoria-traces-single \
  --repo https://victoriametrics.github.io/helm-charts/ \
  --namespace victoriatraces --create-namespace \
  --values values.yaml

Ingesting Traces

Send spans using the OpenTelemetry OTLP/HTTP endpoint. Derive the timestamps from the current time so the span stays inside the default retention window, otherwise older spans are dropped:

START_NS="$(date +%s)000000000"
END_NS="$(date +%s)500000000"

cat > spans.json <<EOF
{"resourceSpans":[{"resource":{"attributes":[{"key":"service.name","value":{"stringValue":"checkout"}}]},
"scopeSpans":[{"spans":[{"traceId":"5b8efff798038103d269b633813fc60c","spanId":"eee19b7ec3c1b174",
"name":"GET /cart","kind":2,"startTimeUnixNano":"${START_NS}","endTimeUnixNano":"${END_NS}"}]}]}]}
EOF

curl -X POST "http://localhost:10428/insert/opentelemetry/v1/traces" \
  -H "Content-Type: application/json" \
  --data-binary @spans.json

Querying Traces

Query traces through the Jaeger-compatible API:

curl "http://localhost:10428/select/jaeger/api/services"

Documentation and Resources

• VictoriaTraces Official Documentation
• VictoriaTraces Quick Start
• VictoriaMetrics Helm Charts
• VictoriaTraces Helm chart

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.