Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bitnami/postgresql:17] POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable #74810

Closed
icronje opened this issue Nov 12, 2024 · 1 comment
Closed
Assignees
Labels
solved tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@icronje
Copy link

icronje commented Nov 12, 2024

Name and Version

bitnami/postgresql:17

What architecture are you using?

amd64

What steps will reproduce the bug?

  1. Use the attached docker-compose.yml file to instantiate an odoo ERP server instance.
  2. Monitor the docker logfile for the postgresql container.

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.

@icronje icronje added the tech-issues The user has a technical issue about an application label Nov 12, 2024
@github-actions github-actions bot added the triage Triage is needed label Nov 12, 2024
@icronje icronje changed the title POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable [bitnami/postgresql:17] POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable Nov 12, 2024
@icronje
Copy link
Author

icronje commented Nov 12, 2024

This is a duplicate of issue #74804. Closing to avoid duplication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

2 participants