[bitnami/postgresql] Release postgresql-16.4.0-debian-12-r25 cause issue with unexpected POSTGRESQL_REPLICATION_USE_PASSFILE

[jonesbusy]

Name and Version

bitnami/postgresql:16.4.0-debian-12-r25

What architecture are you using?

None

What steps will reproduce the bug?

Hi,

Upgrade from postgresql-16.4.0-debian-12-r24 to postgresql-16.4.0-debian-12-r25 cause issue with

POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable

For some reason this was added on https://github.com/bitnami/containers/pull/74787/files#diff-bfae4bf6b63bbf56c7572b773c8f5ce5088f09b8044edc934f49f5aacd26442aR395 but not sure why

Thanks

What is the expected behavior?

No response

What do you see instead?

POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable

Additional information

No response

[jonesbusy]

I lost full logs (only screenshot), but this occur exactly at https://github.com/bitnami/containers/pull/74787/files#diff-bfae4bf6b63bbf56c7572b773c8f5ce5088f09b8044edc934f49f5aacd26442aR395

[val-pez]

I had the same, and was using docker compose. I fixed it by setting:

    environment:
      - POSTGRESQL_REPLICATION_USE_PASSFILE=false

[azhalm94]

This is strange, when running the container locally is Ok, but have this issue with Github workflow

[jeffersonfelixdev]

Same problem here, I tested various versions (13,14,15,16). Same error

[jeffersonfelixdev]

This is strange, when running the container locally is Ok, but have this issue with Github workflow

probably you are using an old version of image in cache. This error started today

[eulixir]

Something changed in the latest version. I followed the same steps as @val-pez, and it worked!

I’m using POSTGRESQL_REPLICATION_USE_PASSFILE: "no" in my postgres image, and that fixed the issue.

[jeffersonfelixdev]

Something changed in the latest version. I followed the same steps as @val-pez, and it worked!

I’m using POSTGRESQL_REPLICATION_USE_PASSFILE: "no" in my postgres image, and that fixed the issue.

Worked!

[carrodher]

Thank you for reaching out. We’re currently tracking this issue in another support ticket. To keep all updates centralized and ensure efficient troubleshooting, we’ll close this ticket as a duplicate. Please refer to ticket #74788 for ongoing updates and further assistance on this matter.

About the issue itself, we're looking into it and we'll update that ticket with our findings. We appreciate your patience and cooperation!