You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The postgresql container fails to start and in the logfile, the following can be seen:
During startup, the following error can be seen:
<container_name> | postgresql 15:24:11.33 INFO ==> Configuring replication parameters
<container_Name> | /opt/bitnami/scripts/libpostgresql.sh: line 395: POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable
Additional information
It seems like the change which was committed into the main branch as part of Release postgresql-17.0.0-debian-12-r13 #74786, introduced this behaviour.
The previous version of the image worked fine.
The text was updated successfully, but these errors were encountered:
icronje
changed the title
POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable
[bitnami/postgresql:17] POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable
Nov 12, 2024
Name and Version
bitnami/postgresql:17
What architecture are you using?
amd64
What steps will reproduce the bug?
docker-compose.zip
What is the expected behavior?
The container should start without failure.
What do you see instead?
The postgresql container fails to start and in the logfile, the following can be seen:
During startup, the following error can be seen:
<container_name> | postgresql 15:24:11.33 INFO ==> Configuring replication parameters
<container_Name> | /opt/bitnami/scripts/libpostgresql.sh: line 395: POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable
Additional information
It seems like the change which was committed into the main branch as part of Release postgresql-17.0.0-debian-12-r13 #74786, introduced this behaviour.
The previous version of the image worked fine.
The text was updated successfully, but these errors were encountered: