[bitnami/postgresql] Release 11.19.0-debian-11-r2 (#24348)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot 2023-02-17 18:46:22 +01:00 committed by GitHub
parent 029787f1a4
commit a17431f346
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 13 additions and 13 deletions

View File

@ -4,11 +4,11 @@ ARG EXTRA_LOCALES
ARG TARGETARCH
ARG WITH_ALL_LOCALES="no"
LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
org.opencontainers.image.description="Application packaged by Bitnami" \
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2023-02-17T17:18:05Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="11.19.0-debian-11-r1" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/postgresql" \
org.opencontainers.image.ref.name="11.19.0-debian-11-r2" \
org.opencontainers.image.title="postgresql" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="11.19.0"
@ -24,8 +24,8 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl libbsd0 libbz2-1.0 libedit2 libffi7 libgcc-s1 libgmp10 libgnutls30 libhogweed6 libicu67 libidn2-0 libldap-2.4-2 liblz4-1 liblzma5 libmd0 libncurses6 libnettle8 libp11-kit0 libpcre3 libreadline8 libsasl2-2 libsqlite3-0 libssl1.1 libstdc++6 libtasn1-6 libtinfo6 libunistring2 libuuid1 libxml2 libxslt1.1 libzstd1 locales procps zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
COMPONENTS=( \
"gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
"postgresql-11.19.0-0-linux-${OS_ARCH}-debian-11" \
"gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
"postgresql-11.19.0-1-linux-${OS_ARCH}-debian-11" \
) && \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \

View File

@ -1,16 +1,16 @@
{
"gosu": {
"arch": "amd64",
"digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
"digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
"distro": "debian-11",
"type": "NAMI",
"version": "1.16.0-1"
"version": "1.16.0-2"
},
"postgresql": {
"arch": "amd64",
"digest": "5143fd81dd6cd0caf1d8235478f1921647ccf4b7c6e6d031da034cc5d6b8ba77",
"digest": "15007e644773293a27e4c9c41dcd204805276e3097d68980213ad6562262274c",
"distro": "debian-11",
"type": "NAMI",
"version": "11.19.0-0"
"version": "11.19.0-1"
}
}

View File

@ -133,7 +133,7 @@ docker run -it --rm \
bitnami/postgresql:latest psql -h postgresql-server -U postgres
```
### Using Docker Compose
### Using a Docker Compose file
When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new `bridge` network named `app-tier`. In this example we assume that you want to connect to the PostgreSQL server from your own custom application image which is identified in the following snippet by the service name `myapp`.
@ -512,7 +512,7 @@ When enabling TLS, PostgreSQL will support both standard and encrypted traffic b
1. Using `docker run`
```console
docker run \
$ docker run \
-v /path/to/certs:/opt/bitnami/postgresql/certs \
-e ALLOW_EMPTY_PASSWORD=yes \
-e POSTGRESQL_ENABLE_TLS=yes \
@ -713,7 +713,7 @@ The Bitnami PostgreSQL container allows two different sets of environment variab
| POSTGRESQL_SYNCHRONOUS_COMMIT_MODE | POSTGRES_SYNCHRONOUS_COMMIT_MODE |
| POSTGRESQL_SHUTDOWN_MODE | POSTGRES_SHUTDOWN_MODE |
> *IMPORTANT*: Changing the `POSTGRES_USER` will not change the owner of the database that will continue being the `postgres` user. In order to change the database owner, please access using `postgres` as user (`psql -U postgres ...`) and execute the following command:
> *IMPORTANT*: Changing the `POSTGRES_USER` will not change the owner of the database that will continue being the `postgres` user. In order to change the database owner, please access using `postgres` as user (`$ psql -U postgres ...`) and execute the following command:
```console
alter database POSTGRES_DATABASE owner to POSTGRES_USER;