sourcemation/alertmanagerAlertmanager is a component of the Prometheus monitoring system that handles alerts sent by client applications such as the Prometheus server. It takes care of deduplicating, grouping, and routing them to the correct receiver integrations such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts.
This Alertmanager distribution is provided by the Sourcemation packaging team, built on a secure Debian 13 Slim base image with version 0.28.1.
Run a temporary container with Alertmanager:
bashdocker run --rm -it -p 9093:9093 sourcemation/alertmanager:latest
The Alertmanager web interface will be available at http://localhost:9093.
Run Alertmanager with persistent storage:
bashdocker run -d --name alertmanager \ -p 9093:9093 \ -v /path/to/your/data:/alertmanager \ sourcemation/alertmanager:latest
Run with custom configuration file:
bashdocker run -d --name alertmanager \ -p 9093:9093 \ -v /path/to/your/alertmanager.yml:/etc/alertmanager/alertmanager.yml \ -v /path/to/your/data:/alertmanager \ sourcemation/alertmanager:latest
Run with additional command line arguments:
bashdocker run -d --name alertmanager \ -p 9093:9093 \ -v /path/to/your/data:/alertmanager \ sourcemation/alertmanager:latest \ --config.file=/etc/alertmanager/alertmanager.yml \ --storage.path=/alertmanager \ --web.listen-address=:9093 \ --cluster.listen-address=0.0.0.0:9094 \ --log.level=info
Run Alertmanager in cluster mode:
bash# Node 1 docker run -d --name alertmanager-1 \ -p 9093:9093 -p 9094:9094 \ -v /path/to/your/data1:/alertmanager \ sourcemation/alertmanager:latest \ --config.file=/etc/alertmanager/alertmanager.yml \ --storage.path=/alertmanager \ --cluster.listen-address=0.0.0.0:9094 \ --cluster.peer=alertmanager-2:9094 # Node 2 docker run -d --name alertmanager-2 \ -p 9095:9093 -p 9096:9094 \ -v /path/to/your/data2:/alertmanager \ sourcemation/alertmanager:latest \ --config.file=/etc/alertmanager/alertmanager.yml \ --storage.path=/alertmanager \ --web.listen-address=:9093 \ --cluster.listen-address=0.0.0.0:9094 \ --cluster.peer=alertmanager-1:9094
This image uses the following environment variables:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
This image exposes the following ports:
Please note that the ports need to be either manually forwarded with the -p option or let Docker choose some for you with the -P option.
The container includes a default alertmanager.yml configuration file located at /etc/alertmanager/alertmanager.yml. You can override this by mounting your own configuration file to this path.
Example minimal configuration:
yamlglobal: smtp_smarthost: 'localhost:587' smtp_from: '***' route: group_by: ['alertname'] group_wait: 10s group_interval: 10s repeat_interval: 1h receiver: 'web.hook' receivers: - name: 'web.hook' webhook_configs: - url: '[***]
This image runs as the nobody user (non-root) for enhanced security. The data directory /alertmanager is writable by the nobody group.
This image includes the following tools:
Example amtool usage:
bash# List all alerts docker exec alertmanager amtool alert query # Silence an alert docker exec alertmanager amtool silence add alertname="HighErrorRate" # Show configuration docker exec alertmanager amtool config show
We'd love for you to contribute! You can request new features, report bugs, or submit a pull request with your contribution to this image on the Sourcemation GitHub repository.
Disclaimer: The sourcemation/alertmanager image is not affiliated with the Alertmanager project. The respective companies and organisations own the trademarks mentioned in the offering. The sourcemation/alertmanager image is a separate project and is maintained by Sourcemation.
A detailed risk analysis report of the image and its components can be found on the Sourcemation platform.
For more information, check out the overview of Alertmanager page.
The base license for the solution (Alertmanager) is the Apache License 2.0. The licenses for each component shipped as part of this image can be found on the image's appropriate Sourcemation entry.


探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
manifest unknown
TLS 证书失败
DNS 超时
410 Gone 排查
402 与流量用尽
401 认证失败
429 限流
D-Bus 凭证提示
413 与超大单层
来自真实用户的反馈,见证轩辕镜像的优质服务