Chainguard Image for jaeger-fips

Chainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.

Download this Image

This image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/jaeger-fips:latest

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

Components

Jaeger provides multiple components;

jaeger-fips-agent
jaeger-fips-all-in-one
jaeger-fips-anonymizer
jaeger-fips-collector
jaeger-fips-es-index-cleaner
jaeger-fips-ingester
jaeger-fips-query
jaeger-fips-remote-storage
jaeger-fips-tracegen

Using Jaeger

Jaeger provides docker images and a helm chart for installation. It can be installed separately with all its components or using a single image with all components bundled in. The bundled component is referred to as All-In-One

Jaeger All In One

This image, designed as a bundle, launches the Jaeger UI, collector, query, and agent, with an in memory storage component. jaeger-all-in-one

Either component can be run directly as docker containers or deployed to Kubernetes with helm. Helm chart is located here https://jaegertracing.github.io/helm-charts. To use them, simply replace the appropriate image: path with the Chainguard specific Jaeger image. Below is an example values file for doing this with helm:

allInOne:
    enabled: true
    image:
    repository: cgr.dev/chainguard/jaeger-fips-all-in-one
    tag: latest
agent:
    enabled: false
collector:
    enabled: false
query:
    enabled: false
storage:
    type: "memory"
# Hotrod is a test application
hotrod:
    enabled: true

Using the above values, the helm commands become, to install Jaeger All In One:

helm repo add jaegertracing https://jaegertracing.github.io/helm-charts

helm upgrade --install jaeger jaegertracing/jaeger \
  --history-max 3 \
  --set provisionDataStore.cassandra=false \
  --set allInOne.enabled=true \
  --set storage.type=memory \
  --set agent.enabled=false \
  --set collector.enabled=false \
  --set query.enabled=false \
  --values jaeger-values.yaml

Jaeger Standalone Components:

agent:
    image:
    repository: cgr.dev/chainguard/jaeger-fips-agent
    tag: latest
collector:
    image:
    repository: cgr.dev/chainguard/jaeger-fips-collector
    tag: latest
query:
    image:
    repository: cgr.dev/chainguard/jaeger-fips-query
    tag: latest
storage:
    type: "memory"
hotrod:
    enabled: true
cassandra:
    config:
    cluster_size: 1

Using the above values, the helm commands become, to install Jaeger with standalone components:

helm repo add jaegertracing https://jaegertracing.github.io/helm-charts

helm upgrade --install jaeger jaegertracing/jaeger \
  --create-namespace \
  --namespace jaeger \
  --history-max 3 \
  --set hotrod.enabled=true \
  --set storage.type=memory  --set cassandra.config.cluster_size=1 \
  --values jaeger-values.yaml

For more configuration options in installing the jaeger helm chart, please refer to the helm upstream doc

NOTE: Setting the tag to "latest" is not recommended, and only shown for illustrative purposes.

Contact Support

If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.

What are Chainguard Images?

Chainguard Images are a collection of container images designed for security and minimalism.

Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.

The main features of Chainguard Images include:

• Minimal design, with no unnecessary software bloat
• Automated nightly builds to ensure Images are completely up-to-date and contain all available security patches
• High quality build-time SBOMs (software bills of materials) attesting the provenance of all artifacts within the Image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

-dev Variants

As mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev variant which does include a shell and package manager.

Although the -dev image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.

That being said, it’s worth noting that -dev variants of Chainguard Images are completely fine to run in production environments. After all, the -dev variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.

Learn More

To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.