public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-19 09:27:16 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/postgresql-repmgr] Release 18.3.0-debian-12-r12 (#92466)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-04-15 05:33:57 +02:00
committed by GitHub
parent 07a2f6935a
commit 99838818d7
2 changed files with 13 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/postgresql-repmgr/18/debian-12/Dockerfile
+3 -3
View File
@@ -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-04-08T20:46:52Z" \
org.opencontainers.image.created="2026-04-15T01:45:24Z" \
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-12-linux-${OS_ARCH}-debian-12" \
"postgresql-repmgr-18.3.0-13-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="11" \
IMAGE_REVISION="12" \
LANG="en_US.UTF-8" \
LANGUAGE="en_US:en" \
NSS_WRAPPER_LIB="/opt/bitnami/common/lib/libnss_wrapper.so" \
bitnami/postgresql-repmgr/README.md
+10 -12
View File
@@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name postgresql-repmgr bitnami/postgresql-repmgr:latest
```
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/postgresql-repmgr/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/postgresql-repmgr/docker-compose.yml)
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/postgresql-ha).
You can find the default credentials and available configuration options in the [Environment Variables](#environment-variables) section.
## Why use Bitnami Secure Images?
@@ -46,10 +54,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami PostgreSQL HA Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/postgresql-ha).
## Persisting your application
If you remove the container all your data 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.
@@ -322,7 +326,7 @@ Apart of using a custom `repmgr.conf`, `postgresql.conf` or `pg_hba.conf`, you c
### Adding extra services to base docker-compose.yaml
It is possible to add extra services to the provided `docker-compose.yaml` file, like [a witness node](https://repmgr.org/docs/4.3/repmgrd-witness-server.html). When adding the new service, please take into account the cluster set up process relays on the `REPMGR_NODE_ID_START_SEED` environment variable plus the service ID in the name (if present, or zero (`0`) by default) to assign cluster's ID to each service/node involved on it. In the case of docker-compose based clusters, this may lead to collisions in the internal IDs in case two or more services share the same ID in their names, making the service initialization process to fail. This isn't an issue on Kubernetes environments, as the Kubernetes controller enumerates the pods with different ID numbers by default.
It is possible to add extra services like [a witness node](https://repmgr.org/docs/4.3/repmgrd-witness-server.html). When adding the new service, please take into account the cluster set up process relays on the `REPMGR_NODE_ID_START_SEED` environment variable plus the service ID in the name (if present, or zero (`0`) by default) to assign cluster's ID to each service/node involved on it. In the case of docker-compose based clusters, this may lead to collisions in the internal IDs in case two or more services share the same ID in their names, making the service initialization process to fail. This isn't an issue on Kubernetes environments, as the Kubernetes controller enumerates the pods with different ID numbers by default.
We recommend setting a different value for the `REPMGR_NODE_ID_START_SEED` in those nodes, or ensuring no services names use repeated numbers.
@@ -336,13 +340,7 @@ The Bitnami PostgreSQL HA Docker image from the [Bitnami Secure Images](https://
## Logging
The Bitnami PostgreSQL HA Docker image sends the container logs to `stdout`. To view the logs:
```console
docker logs pg-0
```
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.
The Bitnami PostgreSQL HA Docker image sends the container logs to the `stdout`. 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.
## Notable Changes