mirror of
https://github.com/bitnami/containers.git
synced 2026-02-27 15:07:25 +08:00
0.23.0-debian-10-r71 release
This commit is contained in:
Bitnami Bot
@@ -19,7 +19,7 @@ RUN chmod g+rwX /opt/bitnami
|
||||
|
||||
RUN mkdir -p /opt/bitnami/alertmanager/data/ && chmod g+rwX /opt/bitnami/alertmanager/data/
|
||||
ENV BITNAMI_APP_NAME="alertmanager" \
|
||||
BITNAMI_IMAGE_VERSION="0.23.0-debian-10-r70" \
|
||||
BITNAMI_IMAGE_VERSION="0.23.0-debian-10-r71" \
|
||||
PATH="/opt/bitnami/alertmanager/bin:$PATH"
|
||||
|
||||
EXPOSE 9093
|
||||
|
||||
@@ -1,17 +1,18 @@
|
||||
# AlertManager packaged by Bitnami
|
||||
|
||||
# What is Alertmanager?
|
||||
## What is AlertManager?
|
||||
|
||||
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 such as email, PagerDuty, or OpsGenie. It also takes care of silencing and inhibition of alerts.
|
||||
> 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.
|
||||
|
||||
[https://github.com/prometheus/alertmanager](https://github.com/prometheus/alertmanager)
|
||||
[Overview of AlertManager](https://github.com/prometheus/alertmanager)
|
||||
|
||||
# TL;DR
|
||||
## TL;DR
|
||||
|
||||
```console
|
||||
$ docker run --name alertmanager bitnami/alertmanager:latest
|
||||
```
|
||||
|
||||
# Why use Bitnami Images?
|
||||
## Why use Bitnami Images?
|
||||
|
||||
* Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
|
||||
* With Bitnami images the latest bug fixes and features are available as soon as possible.
|
||||
@@ -23,20 +24,20 @@ $ docker run --name alertmanager bitnami/alertmanager:latest
|
||||
|
||||
> This [CVE scan report](https://quay.io/repository/bitnami/alertmanager?tab=tags) contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.
|
||||
|
||||
# Why use a non-root container?
|
||||
## Why use a non-root container?
|
||||
|
||||
Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://docs.bitnami.com/tutorials/work-with-non-root-containers/).
|
||||
|
||||
# Supported tags and respective `Dockerfile` links
|
||||
## Supported tags and respective `Dockerfile` links
|
||||
|
||||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
|
||||
|
||||
|
||||
* [`0`, `0-debian-10`, `0.23.0`, `0.23.0-debian-10-r70`, `latest` (0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-alertmanager/blob/0.23.0-debian-10-r70/0/debian-10/Dockerfile)
|
||||
* [`0`, `0-debian-10`, `0.23.0`, `0.23.0-debian-10-r71`, `latest` (0/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-alertmanager/blob/0.23.0-debian-10-r71/0/debian-10/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/alertmanager GitHub repo](https://github.com/bitnami/bitnami-docker-alertmanager).
|
||||
|
||||
# Get this image
|
||||
## Get this image
|
||||
|
||||
The recommended way to get the Bitnami Alertmanager Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/alertmanager).
|
||||
|
||||
@@ -56,7 +57,7 @@ If you wish, you can also build the image yourself.
|
||||
$ docker build -t bitnami/alertmanager:latest 'https://github.com/bitnami/bitnami-docker-alertmanager.git#master:0/debian-10'
|
||||
```
|
||||
|
||||
# Persisting your application
|
||||
## Persisting your application
|
||||
|
||||
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.
|
||||
|
||||
@@ -70,21 +71,21 @@ $ docker run -v /path/to/alertmanager-persistence:/opt/bitnami/data bitnami/aler
|
||||
|
||||
> 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
|
||||
## 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.
|
||||
|
||||
Containers attached to the same network can communicate with each other using the container name as the hostname.
|
||||
|
||||
## Using the Command Line
|
||||
### Using the Command Line
|
||||
|
||||
### Step 1: Create a network
|
||||
#### Step 1: Create a network
|
||||
|
||||
```console
|
||||
$ docker network create alertmanager-network --driver bridge
|
||||
```
|
||||
|
||||
### Step 2: Launch the Alertmanager container within your network
|
||||
#### Step 2: Launch the Alertmanager container within your network
|
||||
|
||||
Use the `--network <NETWORK>` argument to the `docker run` command to attach the container to the `alertmanager-network` network.
|
||||
|
||||
@@ -92,11 +93,11 @@ Use the `--network <NETWORK>` argument to the `docker run` command to attach the
|
||||
$ docker run --name alertmanager-node1 --network alertmanager-network bitnami/alertmanager:latest
|
||||
```
|
||||
|
||||
### Step 3: Run another containers
|
||||
#### Step 3: Run another containers
|
||||
|
||||
We can launch another containers using the same flag (`--network NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network.
|
||||
|
||||
# Configuration
|
||||
## Configuration
|
||||
|
||||
The configuration can easily be setup by mounting your own configuration file on the directory `/opt/bitnami/alertmanager/conf/`:
|
||||
|
||||
@@ -120,11 +121,11 @@ services:
|
||||
|
||||
Configuration is yaml based. The full documentation of the configuration can be found [here](https://prometheus.io/docs/alerting/configuration/).
|
||||
|
||||
## Amtool
|
||||
### Amtool
|
||||
|
||||
`amtool` is a cli tool for interacting with the alertmanager api. It is bundled with all releases of alertmanager.
|
||||
|
||||
# Logging
|
||||
## Logging
|
||||
|
||||
The Bitnami alertmanager Docker image sends the container logs to the `stdout`. To view the logs:
|
||||
|
||||
@@ -134,19 +135,19 @@ $ docker logs alertmanager
|
||||
|
||||
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
|
||||
|
||||
# Maintenance
|
||||
## Maintenance
|
||||
|
||||
## Upgrade this image
|
||||
### Upgrade this image
|
||||
|
||||
Bitnami provides up-to-date versions of alertmanager, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.
|
||||
|
||||
### Step 1: Get the updated image
|
||||
#### Step 1: Get the updated image
|
||||
|
||||
```console
|
||||
$ docker pull bitnami/alertmanager:latest
|
||||
```
|
||||
|
||||
### Step 2: Stop and backup the currently running container
|
||||
#### Step 2: Stop and backup the currently running container
|
||||
|
||||
Stop the currently running container using the command
|
||||
|
||||
@@ -162,13 +163,13 @@ $ rsync -a /path/to/alertmanager-persistence /path/to/alertmanager-persistence.b
|
||||
|
||||
You can use this snapshot to restore the database state should the upgrade fail.
|
||||
|
||||
### Step 3: Remove the currently running container
|
||||
#### Step 3: Remove the currently running container
|
||||
|
||||
```console
|
||||
$ docker rm -v alertmanager
|
||||
```
|
||||
|
||||
### Step 4: Run the new image
|
||||
#### Step 4: Run the new image
|
||||
|
||||
Re-create your container from the new image, [restoring your backup](#restoring-a-backup) if necessary.
|
||||
|
||||
@@ -176,11 +177,11 @@ Re-create your container from the new image, [restoring your backup](#restoring-
|
||||
$ docker run --name alertmanager bitnami/alertmanager:latest
|
||||
```
|
||||
|
||||
# Contributing
|
||||
## Contributing
|
||||
|
||||
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/bitnami-docker-alertmanager/issues), or submit a [pull request](https://github.com/bitnami/bitnami-docker-alertmanager/pulls) with your contribution.
|
||||
|
||||
# Issues
|
||||
## Issues
|
||||
|
||||
If you encountered a problem running this container, you can file an [issue](https://github.com/bitnami/bitnami-docker-alertmanager/issues/new). For us to provide better support, be sure to include the following information in your issue:
|
||||
|
||||
@@ -190,7 +191,7 @@ If you encountered a problem running this container, you can file an [issue](htt
|
||||
- Version of this container
|
||||
- The command you used to run the container, and any relevant output you saw (masking any sensitive information)
|
||||
|
||||
# License
|
||||
## License
|
||||
Copyright (c) 2021 Bitnami
|
||||
|
||||
Licensed under the Apache License, Version 2.0 (the "License");
|
||||
|
||||
Reference in New Issue
Block a user