Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-02-14 16:47:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/alertmanager] Release 0.25.0-debian-11-r30 (#27532)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2023-03-18 22:00:27 +01:00
committed by GitHub
parent c89d9cca57
commit f0834d755b
3 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
bitnami/alertmanager/0/debian-11/Dockerfile
View File

@@ -3,10 +3,10 @@ FROM docker.io/bitnami/minideb:bullseye
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-03-13T21:56:17Z" \
org.opencontainers.image.created="2023-03-18T20:37:32Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="0.25.0-debian-11-r29" \
org.opencontainers.image.ref.name="0.25.0-debian-11-r30" \
org.opencontainers.image.title="alertmanager" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="0.25.0"
@@ -22,7 +22,7 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl procps
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"alertmanager-0.25.0-2-linux-${OS_ARCH}-debian-11" \
"alertmanager-0.25.0-3-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

4
bitnami/alertmanager/0/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@@ -1,9 +1,9 @@
{
"alertmanager": {
"arch": "amd64",
"digest": "b30e160c42f3b6fd56995945a7d08e90c797eff0fc471c03d2d6664425cbc237",
"digest": "eca4c49953d98d2dfec300b2b42a9d7259afe6df69fe9339da6941fd036858a7",
"distro": "debian-11",
"type": "NAMI",
"version": "0.25.0-2"
"version": "0.25.0-3"
}
}

5
bitnami/alertmanager/README.md
View File

@@ -5,7 +5,6 @@
> The Alertmanager 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.
[Overview of AlertManager](https://github.com/prometheus/alertmanager)
Trademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.
## TL;DR
@@ -61,12 +60,12 @@ docker build -t bitnami/APP:latest .
If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
For persistence you should mount a volume at the `/opt/bitnami/data` path. The above examples define a docker volume namely `alertmanager_data`. The Alertmanager application state will persist as long as this volume is not removed.
For persistence you should mount a volume at the `/opt/bitnami/alertmanager/data` path. The above examples define a docker volume namely `alertmanager_data`. The Alertmanager application state will persist as long as this volume is not removed.
To avoid inadvertent removal of this volume you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data.
```console
docker run -v /path/to/alertmanager-persistence:/opt/bitnami/data bitnami/alertmanager:latest
docker run -v /path/to/alertmanager-persistence:/opt/bitnami/alertmanager/data bitnami/alertmanager:latest
```
> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`.