Skip to content

[bitnami/postgresql] pgbackrest installed and configured for backups #75145

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

Closed
fidalgo opened this issue Nov 23, 2024 · 8 comments
Closed

[bitnami/postgresql] pgbackrest installed and configured for backups #75145

fidalgo opened this issue Nov 23, 2024 · 8 comments
Assignees

Comments

@fidalgo
Copy link
Contributor

fidalgo commented Nov 23, 2024

Name and Version

bitnami/postgresql:17

What is the problem this feature will solve?

The image does not have any backup mechanism in place, despite having pgbackrest installed and available.

What is the feature you are proposing to solve the problem?

I noticed under the bitnami/scripts/postgresql/run-autoctl.sh you can configure the pgbackrest, but this file cannot be run as an entry point command, because the pg_autoctl command is missing.
Also, I'm unsure how pgbackrest gets installed in docker in the first place, so I cannot offer a better suggestion at the moment.

@github-actions github-actions bot added the triage Triage is needed label Nov 23, 2024
@carrodher
Copy link
Member

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

@fidalgo
Copy link
Contributor Author

fidalgo commented Nov 28, 2024

@carrodher thanks for the reply, I can try to put a PR together, but I need to understand how packages are installed in the first place.

So to start, how does PgBackRest get installed into the Docker image? I've searched the codebase and cannot find any reference, so it would be great if someone from the team could provide a tip.

@github-actions github-actions bot removed the triage Triage is needed label Dec 11, 2024
@github-actions github-actions bot assigned gongomgra and unassigned carrodher Dec 11, 2024
Copy link

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.

@github-actions github-actions bot added the stale 15 days without activity label Dec 27, 2024
@fidalgo
Copy link
Contributor Author

fidalgo commented Dec 30, 2024

@carrodher Is there any doc where I can get more info about how the pgBackRest is added to the docker image?

@github-actions github-actions bot removed the stale 15 days without activity label Dec 31, 2024
Copy link

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.

@github-actions github-actions bot added the stale 15 days without activity label Jan 16, 2025
@gongomgra
Copy link
Contributor

Hi @fidalgo,

According to this official pg_auto_failover discussion, the extension doesn't support PostgreSQL 17.x yet, that's why it is not included in our images at this moment. It looks like they are working on adding support for it. We would need to wait until a new pg_auto_failover version is released with support for PostgreSQL 17.x so we can add it to our images.

hapostgres/pg_auto_failover#1061

About how pgbackrest, pg_auto_failover, and other extensions are included in the final image, they are built on our side as part of our automated pipeline along with PostgreSQL, and it is not possible to contribute to these steps. You can extend our PostgreSQL image to build the extension if you want to test it on your side before we officially release it.

@github-actions github-actions bot removed the stale 15 days without activity label Jan 21, 2025
Copy link

github-actions bot commented Feb 5, 2025

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.

@github-actions github-actions bot added the stale 15 days without activity label Feb 5, 2025
Copy link

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

@bitnami-bot bitnami-bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants