Stopped After Last Update (docker pull)

[MacAlistair-r]

Name and Version

bitnami/postgresql:16.4.0

What architecture are you using?

amd64

What steps will reproduce the bug?

Find running bitnami/postgresql:16.4.0 before the last update then check is it up or not.

What is the expected behavior?

Still working after last update

What do you see instead?

Gives an error message.

2024-11-12T10:45:13.748953515Z postgresql 10:45:13.74 INFO  ==> 
2024-11-12T10:45:13.751928062Z postgresql 10:45:13.75 INFO  ==> Welcome to the Bitnami postgresql container
2024-11-12T10:45:13.754636478Z postgresql 10:45:13.75 INFO  ==> Subscribe to project updates by watching https://github.com/bitnami/containers
2024-11-12T10:45:13.757346015Z postgresql 10:45:13.75 INFO  ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
2024-11-12T10:45:13.760750090Z postgresql 10:45:13.76 INFO  ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit https://bitnami.com/enterprise
2024-11-12T10:45:13.762656862Z postgresql 10:45:13.76 INFO  ==> 
2024-11-12T10:45:13.786012135Z postgresql 10:45:13.78 INFO  ==> ** Starting PostgreSQL setup **
2024-11-12T10:45:13.804393601Z postgresql 10:45:13.80 INFO  ==> Validating settings in POSTGRESQL_* env vars..
2024-11-12T10:45:13.813345338Z postgresql 10:45:13.81 INFO  ==> Loading custom pre-init scripts...
2024-11-12T10:45:13.818764463Z postgresql 10:45:13.81 INFO  ==> Initializing PostgreSQL database...
2024-11-12T10:45:13.838551556Z postgresql 10:45:13.83 INFO  ==> pg_hba.conf file not detected. Generating it...
2024-11-12T10:45:13.840502222Z postgresql 10:45:13.84 INFO  ==> Generating local authentication configuration
2024-11-12T10:45:13.857660983Z postgresql 10:45:13.85 INFO  ==> Deploying PostgreSQL with persisted data...
2024-11-12T10:45:13.870083694Z postgresql 10:45:13.86 INFO  ==> Configuring replication parameters
2024-11-12T10:45:13.897968389Z /opt/bitnami/scripts/libpostgresql.sh: line 395: POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable

Additional information

It literally stopped my 1 year running 7 databases, all of them are on different environment. They all using same docker image and they stopped with that error after you released a new docker image (15 min ago)
PS Note:
Bitnami I love you but sometimes you make me crazy.

[ivan-price-acted]

hi there, we're getting this too !

[MacAlistair-r]

image: docker.io/bitnami/postgresql:16@sha256:ef5d01eb7ce08e8e5a1e82b8b52f25f9cdabb8a86ca5567eb597aa79ea54d515

you can use this for temporary solution
edit: if you use 16.4

[chrisapplegate]

I'm using pg 14 and get the same error, seems it is this automated change that broke everything

Setting POSTGRESQL_REPLICATION_USE_PASSFILE to off/false in my env (I use it for CI in Github Actions) seems to have sorted this out, but there should be a check in the update to make sure that it doesn't error out if POSTGRESQL_REPLICATION_USE_PASSFILE is not set in the env

[amorillas]

We're having the same issue and we're opting for pinning the version.

[mi-laf]

We have some test environments where we so far just used bitnami/postgresql:latest. Same error there. We are now also pinning the version.

[ddzobov]

same issue, broken on 16.x branch

[aabouzaid]

The issue also happens in 15.8.0.

[rsignavong]

Same issue with version 17

[Takadimi]

Same issue w/ version 16

Workaround for us was setting the env var in the Dockerfile where this is the base image.

ENV POSTGRESQL_REPLICATION_USE_PASSFILE=no

[aabouzaid]

As a workaround without playing with env vars, I've used the named versions (last working images, released 3 days ago):

15.8.0-debian-12-r23
15.7.0-debian-12-r19
14.13.0-debian-12-r22
14.5.0-debian-11-r35

[jamiestarke-anglepoint]

It appears that this was caused by a new required variable that is effectively a breaking change, but released on the existing tags: https://github.com/bitnami/containers/blame/main/bitnami/postgresql/17/debian-12/rootfs/opt/bitnami/scripts/libpostgresql.sh#L395-L398

[jsclayton]

Workaround: add POSTGRESQL_REPLICATION_USE_PASSFILE=false to your environment vars for the container.

[bbeasleyAtZscaler]

How do we add the environment variable when running the chart via helm command? I tried a few options such as:

'['helm', 'upgrade', '--install', '--set', 'primary.extraEnvVars[0].name=POSTGRESQL_REPLICATION_USE_PASSFILE', '--set', 'primary.extraEnvVars[0].value=false', 'postgres', 'bitnami/postgresql']'

and

'['helm', 'upgrade', '--install', '--set', 'primary.extraEnvVars.POSTGRESQL_REPLICATION_USE_PASSFILE=false', 'postgres', 'bitnami/postgresql']'

but, no luck so far.

[ngauje]

Same for bitnami/postgresql:12-debian-12 image :(

[fmulero]

Thank you all for reporting the issue and pointing to the breaking change.

As @jsclayton said, setting the env var POSTGRESQL_REPLICATION_USE_PASSFILE to false or no works. We are working on a new release to fix the root cause. In the next hours, a new tag will be released for all the affected versions. Please be aware of the risks of using rolling tags.

NOTE: Latest release of the bitnami/postgresql chart is not affected.

[fmulero]

These are the new releases:

• [bitnami/postgresql] Release postgresql-17.0.0-debian-12-r15 #74850
• [bitnami/postgresql] Release postgresql-15.8.0-debian-12-r26 #74849
• [bitnami/postgresql] Release postgresql-13.16.0-debian-12-r26 #74848
• [bitnami/postgresql] Release postgresql-16.4.0-debian-12-r27 #74847
• [bitnami/postgresql] Release postgresql-14.13.0-debian-12-r25 #74846
• [bitnami/postgresql] Release postgresql-12.20.0-debian-12-r26 #74845

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.