From 3e610cf6da7e7ee05f38c27aa5b4ca16526ab435 Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Wed, 4 Mar 2026 09:03:09 +0100 Subject: [PATCH] [bitnami/postgresql-repmgr] Release 18.3.0-debian-12-r2 (#91227) Signed-off-by: Bitnami Bot --- bitnami/postgresql-repmgr/18/debian-12/Dockerfile | 6 +++--- bitnami/postgresql-repmgr/README.md | 14 ++++++++------ 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/bitnami/postgresql-repmgr/18/debian-12/Dockerfile b/bitnami/postgresql-repmgr/18/debian-12/Dockerfile index 7b68c2f55169..7828966f8ed4 100644 --- a/bitnami/postgresql-repmgr/18/debian-12/Dockerfile +++ b/bitnami/postgresql-repmgr/18/debian-12/Dockerfile @@ -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-25T20:46:41Z" \ + org.opencontainers.image.created="2026-03-04T07:32:33Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/postgresql-repmgr/README.md" \ org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/postgresql-repmgr" \ @@ -29,7 +29,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \ COMPONENTS=( \ "nss-wrapper-1.1.16-0-linux-${OS_ARCH}-debian-12" \ - "postgresql-repmgr-18.3.0-1-linux-${OS_ARCH}-debian-12" \ + "postgresql-repmgr-18.3.0-2-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -55,7 +55,7 @@ COPY rootfs / RUN /opt/bitnami/scripts/postgresql-repmgr/postunpack.sh ENV APP_VERSION="18.3.0" \ BITNAMI_APP_NAME="postgresql-repmgr" \ - IMAGE_REVISION="1" \ + IMAGE_REVISION="2" \ LANG="en_US.UTF-8" \ LANGUAGE="en_US:en" \ NSS_WRAPPER_LIB="/opt/bitnami/common/lib/libnss_wrapper.so" \ diff --git a/bitnami/postgresql-repmgr/README.md b/bitnami/postgresql-repmgr/README.md index 01cc8fc88c3f..fc4d24954122 100644 --- a/bitnami/postgresql-repmgr/README.md +++ b/bitnami/postgresql-repmgr/README.md @@ -1,7 +1,5 @@ # Bitnami Secure Image for PostgreSQL HA -## What is PostgreSQL HA? - > This PostgreSQL cluster solution includes the PostgreSQL replication manager, an open-source tool for managing replication and failover on PostgreSQL clusters. [Overview of PostgreSQL HA](https://www.postgresql.org) @@ -76,7 +74,7 @@ If you remove the container all your data will be lost, and the next time you ru For persistence you should mount a directory at the `/bitnami/postgresql` path. If the mounted directory is empty, it will be initialized on the first run. -> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`. +> **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 @@ -86,8 +84,12 @@ Containers attached to the same network can communicate with each other using th ## Configuration +The following section describes the supported environment variables + ### Environment variables +The following tables list the main variables you can set. + #### Customizable environment variables | Name | Description | Default Value | @@ -273,7 +275,7 @@ In order to have your custom files inside the docker image you can mount them as In the above commands you may have noticed the use of the `POSTGRESQL_PASSWORD` and `REPMGR_PASSWORD` environment variables. Passing the `POSTGRESQL_PASSWORD` environment variable when running the image for the first time will set the password of the `postgres` user to the value of `POSTGRESQL_PASSWORD` (or the content of the file specified in `POSTGRESQL_PASSWORD_FILE`). In the same way, passing the `REPMGR_PASSWORD` environment variable sets the password of the `repmgr` user to the value of `REPMGR_PASSWORD` (or the content of the file specified in `REPMGR_PASSWORD_FILE`). -> NOTE: Both `postgres` and `repmgr` users are superusers and have full administrative access to the PostgreSQL database. +> **NOTE** Both `postgres` and `repmgr` users are superusers and have full administrative access to the PostgreSQL database. Refer to [Creating a database user on first run](#creating-a-database-user-on-first-run) if you want to set an unprivileged user and a password for the `postgres` user. @@ -285,7 +287,7 @@ By passing the `POSTGRESQL_DATABASE` environment variable when running the image You can also create a restricted database user that only has permissions for the database created with the [`POSTGRESQL_DATABASE`](#creating-a-database-on-first-run) environment variable. To do this, provide the `POSTGRESQL_USERNAME` environment variable. -> NOTE: When `POSTGRESQL_USERNAME` is specified, the `postgres` user is not assigned a password and as a result you cannot login remotely to the PostgreSQL server as the `postgres` user. If you still want to have access with the user `postgres`, please set the `POSTGRESQL_POSTGRES_PASSWORD` environment variable (or the content of the file specified in `POSTGRESQL_POSTGRES_PASSWORD_FILE`). +> **NOTE** When `POSTGRESQL_USERNAME` is specified, the `postgres` user is not assigned a password and as a result you cannot login remotely to the PostgreSQL server as the `postgres` user. If you still want to have access with the user `postgres`, please set the `POSTGRESQL_POSTGRES_PASSWORD` environment variable (or the content of the file specified in `POSTGRESQL_POSTGRES_PASSWORD_FILE`). ### Setting up a HA PostgreSQL cluster with streaming replication and repmgr @@ -307,7 +309,7 @@ A HA PostgreSQL cluster with [Streaming replication](https://www.postgresql.orgd In a HA PostgreSQL cluster you can have one primary and zero or more standby nodes. The primary node is in read-write mode, while the standby nodes are in read-only mode. For best performance its advisable to limit the reads to the standby nodes. -> NOTE: REPMGR_USE_PASSFILE and REPMGR_PASSFILE_PATH will be ignored for Postgresql prior to version 9.6. +> **NOTE** REPMGR_USE_PASSFILE and REPMGR_PASSFILE_PATH will be ignored for Postgresql prior to version 9.6. > > When mounting an external passfile using REPMGR_PASSFILE_PATH, it is necessary to also configure REPMGR_PASSWORD and REPMGR_USERNAME accordingly.