chronograf-fips

packaged by Chainguard

Chainguard Container for chronograf-fips

FIPS-enabled minimal image for Chronograf, the InfluxData monitoring and visualization UI.

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/chronograf-fips:latest

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

Compatibility Notes

The Chainguard chronograf-fips container image is a FIPS-validated drop-in replacement for the official Chronograf image on Docker Hub. The image preserves the upstream entrypoint, CMD, exposed port (8888), data volume (/var/lib/chronograf), and shipped data files (/usr/share/chronograf/{canned,protoboards,resources}). It bundles both the chronograf server and the chronoctl admin CLI, plus the upstream entrypoint.sh so BOLT_PATH and privilege-drop behavior match the upstream image.

FIPS Support

The chronograf-fips Chainguard Container ships with a validated redistribution of the OpenSSL FIPS provider module and is built with the FIPS-validated Go toolchain. For more on FIPS support in Chainguard Containers, including the validation lifecycle, refer to the guide on FIPS-enabled Chainguard Images on Chainguard Academy.

For full configuration documentation, see the upstream Chronograf documentation.

Getting Started

The chronograf-fips Chainguard Container can be deployed using Docker or Helm. Be sure to replace ORGANIZATION with the name of your organization's private repository within the Chainguard Registry.

Using Docker to Deploy

Run the container directly, exposing the UI on port 8888 and persisting the boltdb data via a named volume:

docker run -d \
  --name chronograf \
  -p 8888:8888 \
  -v chronograf-data:/var/lib/chronograf \
  cgr.dev/ORGANIZATION/chronograf-fips:latest

Once running, Chronograf is reachable at http://localhost:8888. Point it at an InfluxDB instance through the UI to begin building dashboards.

Using Helm to Deploy

Chronograf can be deployed to Kubernetes using the official InfluxData Helm chart, overriding the chart's default image with the Chainguard FIPS image. Add the repo:

helm repo add influxdata https://helm.influxdata.com/
helm repo update

Create a values.yaml manifest pointing the chart at the Chainguard FIPS image:

image:
  repository: cgr.dev/ORGANIZATION/chronograf-fips
  tag: latest

Then install the chart:

helm upgrade --install chronograf influxdata/chronograf -f values.yaml

Refer to the Helm chart documentation for the full list of values, including OAuth, ingress, and persistence configuration.

Documentation and Resources

• FIPS-enabled Chainguard Images guide
• Official Chronograf Documentation
• Chronograf Configuration Options
• Chronograf GitHub Repository
• Chronograf on Docker Hub
• InfluxData Chronograf Helm Chart
• Upstream entrypoint.sh source

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.