Chainguard Container for pushprox-fips

Minimal FIPS compliant image with PushProx, a proxy to allow Prometheus to scrape through NAT etc.

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/pushprox-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 pushprox-fips Chainguard image is meant to serve as a drop-in replacement for the PushProx image on DockerHub. Like most Chainguard images, this image is minimal, has few-to-zero CVEs and does not run as the root user.

Prerequisites

• prometheus
• prometheus-node-exporter (component to scrape)

Getting started

To begin, start the PushProx container with a command like the following:

# pushprox-proxy
docker run --rm cgr.dev/ORGANIZATION/pushprox-fips --help

# pushprox-client
docker run --rm --entrypoint="/app/pushprox-client" cgr.dev/ORGANIZATION/pushprox-fips --help

This will return pushprox-proxy and pushprox-client Command-line's usage instructions.

The PushProx client performs scrapes in a network environment that's not directly accessible by Prometheus. The PushProx proxy is accessible by both the Clients and Prometheus. Each client is identified by its fqdn.

Create isolated docker networks and deploy the target service (node_exporter) and the PushProx client on one network. Then deploy PushProx proxy and Prometheus will be deployed on the other.

Prometheus will scrape the target via the proxy. The client will then poll the proxy for scrape requests. The proxy routes the scrape to the client. This scrape request is executed by the client and the response containing metrics is posted to the proxy.

Create isolated networks

docker network create external-net
docker network create internal-net --internal

Deploy node_exporter

docker run -d --name target \
--network internal-net \
cgr.dev/ORGANIZATION/prometheus-node-exporter-fips:latest

Deploy PushProx proxy

docker run -d --name pushprox-proxy \
--network external-net \
-p 8080:8080 \
cgr.dev/ORGANIZATION/pushprox-fips:latest

Deploy PushProx client

docker run -d --name pushprox-client \
--network internal-net \
--entrypoint="/app/pushprox-client" \
cgr.dev/ORGANIZATION/pushprox-fips:latest \
--proxy-url="http://pushprox-proxy:8080" \
--fqdn="target"

Connect client to external network

docker network connect external-net pushprox-client

Deploy prometheus

1. Create prometheus scrape config

cat << EOF > prometheus.yml
global:
  scrape_interval: 30s

scrape_configs:
  - job_name: pushprox
    proxy_url: http://pushprox-proxy:8080
    static_configs:
    - targets: ['target:9100']
EOF

2. Deploy prometheus

docker run -d --name $prometheus_container \
--network external-net \
-p 9090:9090 \
-v ./prometheus.yml:/etc/prometheus/prometheus.yml \
cgr.dev/ORGANIZATION/prometheus-fips:latest \
--config.file=/etc/prometheus/prometheus.yml

Validate target is up and being scraped

curl http://localhost:9090/api/v1/targets | jq -r '.data.activeTargets'

expected response:

[
  {
    "discoveredLabels": {
      "__address__": "target:9100",
      "__metrics_path__": "/metrics",
      "__scheme__": "http",
      "__scrape_interval__": "5s",
      "__scrape_timeout__": "5s",
      "job": "pushprox"
    },
    "labels": {
      "instance": "target:9100",
      "job": "pushprox"
    },
    "scrapePool": "pushprox",
    "scrapeUrl": "http://target:9100/metrics",
    "globalUrl": "http://target:9100/metrics",
    "lastError": "",
    "lastScrape": "2025-07-16T19:59:32.623643339Z",
    "lastScrapeDuration": 0.02758125,
    "health": "up",
    "scrapeInterval": "30s",
    "scrapeTimeout": "30s"
  }
]

Documentation and Resources

• PushProx Repo

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

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.