dhi.io/rancher-pushprox-client
Rancher PushProx Client
Client for PushProx, which lets Prometheus scrape targets behind NAT and firewalls through a proxy
pushed 4 hours ago
linux/amd64, linux/arm64
33.44 MB
for linux/amd64
144
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
-
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Rancher PushProx Client
Rancher PushProx Client is the pushprox-client binary from the PushProx
project. It runs next to Prometheus targets that cannot be scraped directly, such as hosts behind NAT or a firewall. The
client registers with a PushProx proxy and serves Prometheus scrapes that the proxy relays to it. Use it as a sidecar or
DaemonSet alongside the target, or as the rancher-pushprox chart's client component.
This image is a drop-in for rancher/pushprox-client. It keeps the upstream entrypoint and command so
pushprox-client --proxy-url=… works as before. It runs as a non-root user and listens for metrics on port 9369.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.