Chainguard Image for prometheus

Chainguard image for Prometheus, a systems and service monitoring system.

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/prometheus:latest

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

Compatibility Notes

Chainguard's Prometheus image is meant to serve as a drop-in replacement for both the prom/prometheus image and the bitnami/prometheus image. Like most other Chainguard images, the production variant of the Prometheus image comes with only the minimum dependencies needed to function and does not include things like a shell or package manager.

Getting Started

Chainguard's Prometheus image requires a Prometheus configuration file in order to run. It comes with an example configuration file, which is found within the container at /etc/prometheus/prometheus.yml. The values from this example can be found in the Prometheus source tree.

You can test out the image using the example configuration file with the following command. Note that you will need to change ORGANIZATION to align with the name of your organization's private repository within the Chainguard registry:

docker run -p 9090:9090 cgr.dev/ORGANIZATION/prometheus:latest --config.file=/etc/prometheus/prometheus.yml

. . .
time=2024-12-13T01:10:13.001Z level=INFO source=main.go:1224 msg="Server is ready to receive web requests."
time=2024-12-13T01:10:13.001Z level=INFO source=manager.go:168 msg="Starting rule manager..." component="rule manager"

The default port that Prometheus listens on is 9090. By including -p 9090:9090 in the previous command, the application will be exposed on the host at port 9090. You can use your web browser to check whether the Prometheus application is indeed running by navigating to localhost:9090.

Alternatively, you can use a Prometheus configuration file stored locally by mounting a volume, like this:

docker run -p 9090:9090 -v /path/to/local/prometheus.yml:/prometheus.yml cgr.dev/ORGANIZATION/prometheus:latest

Documentation and Resources

• Official Prometheus Documentation
• Prometheus GitHub Repository

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.