run prometheus rootless and distroless
10K+

run prometheus rootless and distroless
Prometheus, a Cloud Native Computing Foundation project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts when specified conditions are observed.

What can I do with this? This image will run Prometheus rootlessβ and distrolessβ , for maximum security and performance. You can either provide your own config file or configure Prometheus directly inline in your compose. If you run the compose example, you can open the following URLβ to see the statistics of your DNS benchmark just like in the screenshot.
Why should I run this image and not the other image(s) that already exist? Good question! Because ...
If you value security, simplicity and optimizations to the extreme, then this image might be for you.
Below you find a comparison between this image and the most used or original one.
| image | size on disk | init default as | distrolessβ | supported architectures |
|---|---|---|---|---|
| 11notes/prometheus | 56MB | 1000:1000 | β | amd64, arm64, armv7 |
| prom/prometheus | 261MB | 65534:65534 | β | amd64, arm64, armv7, ppc64le, riscv64, s390x |
global:
scrape_interval: 10s
scrape_configs:
- job_name: "prometheus"
static_configs:
- targets: ["localhost:3000"]
name: "monitoring"
x-lockdown: &lockdown
# prevents write access to the image itself
read_only: true
# prevents any process within the container to gain more privileges
security_opt:
- "no-new-privileges=true"
services:
prometheus:
depends_on:
adguard:
condition: "service_healthy"
restart: true
image: "11notes/prometheus:3.14.0"
<<: *lockdown
environment:
TZ: "Europe/Zurich"
PROMETHEUS_CONFIG: |-
global:
scrape_interval: 1s
scrape_configs:
- job_name: "dnspyre"
static_configs:
- targets: ["dnspyre:3000"]
volumes:
- "prometheus.etc:/prometheus/etc"
- "prometheus.var:/prometheus/var"
ports:
- "3000:9090/tcp"
networks:
frontend:
restart: "always"
dnspyre:
# for more information about this image checkout:
# https://github.com/11notes/docker-distroless
#
# this image will execute 100k (10 x 10000) queries
# against adguard to fill your Prometheus with some data
depends_on:
prometheus:
condition: "service_healthy"
restart: true
image: "11notes/distroless:dnspyre"
<<: *lockdown
command: "--server adguard -c 10 -n 3 -t A --prometheus ':3000' https://raw.githubusercontent.com/11notes/static/refs/heads/master/src/benchmarks/dns/fqdn/10000"
environment:
TZ: "Europe/Zurich"
networks:
frontend:
adguard:
# for more information about this image checkout:
# https://github.com/11notes/docker-adguard
image: "11notes/adguard:0.107.64"
<<: *lockdown
environment:
TZ: "Europe/Zurich"
volumes:
- "adguard.etc:/adguard/etc"
- "adguard.var:/adguard/var"
tmpfs:
- "/adguard/run:uid=1000,gid=1000"
ports:
- "53:53/udp"
- "53:53/tcp"
- "3010:3000/tcp"
networks:
frontend:
sysctls:
net.ipv4.ip_unprivileged_port_start: 53
restart: "always"
volumes:
prometheus.etc:
prometheus.var:
adguard.etc:
adguard.var:
networks:
frontend:
To find out how you can change the default UID/GID of this container image, consult the RTFMβ .
| Parameter | Value | Description |
|---|---|---|
user | docker | user name |
uid | 1000 | user identifierβ |
gid | 1000 | group identifierβ |
home | /prometheus | home directory of user docker |
| Parameter | Value | Default |
|---|---|---|
TZ | Time Zoneβ | |
DEBUG | Will activate debug option for container image and app (if available) | |
PROMETHEUS_CONFIG (optional) | Will overwrite the default config with the value of this variable if set (inline configβ ) |
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. If you donβt want to change the tag to the latest semverβ , simply use the short versions of semverβ . Instead of using :3.14.0 you can use :3 or :3.14. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version. Which in theory should not introduce breaking changes.
If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
docker pull 11notes/prometheus:3.14.0
docker pull ghcr.io/11notes/prometheus:3.14.0
docker pull quay.io/11notes/prometheus:3.14.0
This image supports unraid by default. Simply add -unraid to any tag and the image will run as 99:100 instead of 1000:1000.
This image supports nobody by default. Simply add -nobody to any tag and the image will run as 65534:65534 instead of 1000:1000.
This image is not based on another image but uses scratchβ as the starting layer. The image consists of the following distroless layers that were added:
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releasesβ for breaking changes. If you have any problems with using this image simply raise an issueβ , thanks. If you have a question or inputs please create a new discussionβ instead of an issue. You can find all my other repositories on githubβ .
created 19.08.2026, 06:10:52 (CET)
Content type
Image
Digest
sha256:3c5a5f2faβ¦
Size
48.4 MB
Last updated
29 days ago
docker pull 11notes/prometheus:3.14.0-nobody