diff --git a/bitnami/alertmanager/0/debian-9/Dockerfile b/bitnami/alertmanager/0/debian-9/Dockerfile index 9e212fd2f40f..f722e0e08177 100644 --- a/bitnami/alertmanager/0/debian-9/Dockerfile +++ b/bitnami/alertmanager/0/debian-9/Dockerfile @@ -12,7 +12,7 @@ RUN ln -sf /opt/bitnami/alertmanager/data /alertmanager RUN mkdir -p /opt/bitnami/alertmanager/data/ && chmod g+rwX /opt/bitnami/alertmanager/data/ ENV BITNAMI_APP_NAME="alertmanager" \ - BITNAMI_IMAGE_VERSION="0.19.0-debian-9-r53" \ + BITNAMI_IMAGE_VERSION="0.19.0-debian-9-r54" \ PATH="/opt/bitnami/alertmanager/bin:$PATH" EXPOSE 9093 diff --git a/bitnami/alertmanager/README.md b/bitnami/alertmanager/README.md index 90cff98db4d1..446b21dce625 100644 --- a/bitnami/alertmanager/README.md +++ b/bitnami/alertmanager/README.md @@ -47,7 +47,7 @@ Learn more about the Bitnami tagging policy and the difference between rolling t * [`0-ol-7`, `0.19.0-ol-7-r64` (0/ol-7/Dockerfile)](https://github.com/bitnami/bitnami-docker-alertmanager/blob/0.19.0-ol-7-r64/0/ol-7/Dockerfile) -* [`0-debian-9`, `0.19.0-debian-9-r53`, `0`, `0.19.0`, `0.19.0-r53`, `latest` (0/debian-9/Dockerfile)](https://github.com/bitnami/bitnami-docker-alertmanager/blob/0.19.0-debian-9-r53/0/debian-9/Dockerfile) +* [`0-debian-9`, `0.19.0-debian-9-r54`, `0`, `0.19.0`, `0.19.0-r54`, `latest` (0/debian-9/Dockerfile)](https://github.com/bitnami/bitnami-docker-alertmanager/blob/0.19.0-debian-9-r54/0/debian-9/Dockerfile) Subscribe to project updates by watching the [bitnami/alertmanager GitHub repo](https://github.com/bitnami/bitnami-docker-alertmanager). @@ -83,6 +83,8 @@ To avoid inadvertent removal of this volume you can [mount host directories as d $ docker run -v /path/to/alertmanager-persistence:/opt/bitnami/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`. + # Connecting to other containers Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa.