Skip to content

draft: fix: migrate away from deprecated bitnami image #32

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Morl99
Copy link
Contributor

@Morl99 Morl99 commented Jul 29, 2025

BREAKING CHANGE: dropping support for postgres 13
BREAKING CHANGE: switching to official postgres image with alpine base

relates to #31

BREAKING CHANGE: dropping support for postgres 13
BREAKING CHANGE: switching to official postgres image with alpine base
@Morl99
Copy link
Contributor Author

Morl99 commented Jul 29, 2025

Since this is a breaking change, I wonder on how and when we should merge this and how we communicate this to reduce suprises by consumers.

@jschirrmacher
Copy link
Contributor

At least, we should add a note in README.

What could happen in the worst case? If someone still uses version 13, they would get the old image, I suppose? How could someone rely on the bitnami base (e.g. extending our image with more packages), they would get errors and hopefully would read the README file at first.

Nice idea to use official PostgreSQL images as the base. Why did we use bitnami in the first place?

@Morl99
Copy link
Contributor Author

Morl99 commented Jul 30, 2025

Yeah, worst case it breaks Dockerfiles of people that use our image at the base or breaks deployments where people rely on Env Variables of the bitnami image.

Good question, because we used bitnami in our project and it seemed like a good choice, I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants