[bitnami/pushgateway] Release 1.11.2-debian-12-r9 (#91387)
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
parent
ec06d73426
commit
3b331f0c5f
|
|
@ -7,7 +7,7 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
|
|||
ARG TARGETARCH
|
||||
|
||||
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
|
||||
org.opencontainers.image.created="2026-02-19T04:04:05Z" \
|
||||
org.opencontainers.image.created="2026-03-06T17:15:29Z" \
|
||||
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
|
||||
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/pushgateway/README.md" \
|
||||
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/pushgateway" \
|
||||
|
|
@ -28,7 +28,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
|
|||
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
|
||||
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
|
||||
COMPONENTS=( \
|
||||
"pushgateway-1.11.2-4-linux-${OS_ARCH}-debian-12" \
|
||||
"pushgateway-1.11.2-5-linux-${OS_ARCH}-debian-12" \
|
||||
) ; \
|
||||
for COMPONENT in "${COMPONENTS[@]}"; do \
|
||||
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
|
||||
|
|
@ -47,7 +47,7 @@ RUN uninstall_packages curl
|
|||
|
||||
ENV APP_VERSION="1.11.2" \
|
||||
BITNAMI_APP_NAME="pushgateway" \
|
||||
IMAGE_REVISION="8" \
|
||||
IMAGE_REVISION="9" \
|
||||
PATH="/opt/bitnami/pushgateway/bin:$PATH"
|
||||
|
||||
EXPOSE 9091
|
||||
|
|
|
|||
|
|
@ -1,7 +1,5 @@
|
|||
# Bitnami Secure Image for Push Gateway
|
||||
|
||||
## What is Push Gateway?
|
||||
|
||||
> The Pushgateway is an intermediary service which allows you to push metrics from jobs which cannot be scraped
|
||||
|
||||
[Overview of Push Gateway](https://prometheus.io/)
|
||||
|
|
@ -108,48 +106,6 @@ docker logs pushgateway
|
|||
|
||||
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
|
||||
|
||||
### Upgrade this image
|
||||
|
||||
Bitnami provides up-to-date versions of pushgateway, 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
|
||||
|
||||
```console
|
||||
docker pull bitnami/pushgateway:latest
|
||||
```
|
||||
|
||||
#### Step 2: Stop and backup the currently running container
|
||||
|
||||
Stop the currently running container using the command
|
||||
|
||||
```console
|
||||
docker stop pushgateway
|
||||
```
|
||||
|
||||
Next, take a snapshot of the persistent volume `/path/to/pushgateway-persistence` using:
|
||||
|
||||
```console
|
||||
rsync -a /path/to/pushgateway-persistence /path/to/pushgateway-persistence.bkp.$(date +%Y%m%d-%H.%M.%S)
|
||||
```
|
||||
|
||||
You can use this snapshot to restore the database state should the upgrade fail.
|
||||
|
||||
#### Step 3: Remove the currently running container
|
||||
|
||||
```console
|
||||
docker rm -v pushgateway
|
||||
```
|
||||
|
||||
#### Step 4: Run the new image
|
||||
|
||||
Re-create your container from the new image, restoring your backup if necessary.
|
||||
|
||||
```console
|
||||
docker run --name pushgateway bitnami/pushgateway:latest
|
||||
```
|
||||
|
||||
## Notable Changes
|
||||
|
||||
### Starting January 16, 2024
|
||||
|
|
|
|||
Loading…
Reference in New Issue