Update 'Hello Postgres cluster' example to replace deprecated `bitnamilegacy` image
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
Research direction
Open running_pg_cluster_in_docker/1. Hello Postgres cluster/docker-compose.yml and inspect the two PostgreSQL service image references. Update both references to soldevelo/postgresql-repmgr:17.6.0, then run the existing Docker Compose example to confirm the cluster still starts with its current configuration.
Written by the indexing model from the issue text.
Description
Hi,
I was exploring your excellent collection of SQL scripts and Docker examples, and I noticed that the running_pg_cluster_in_docker/1. Hello Postgres cluster/docker-compose.yml file uses the bitnamilegacy/postgresql-repmgr:17.6.0 Docker image.
The Problem
As the namespace implies, bitnamilegacy contains deprecated artifacts that are no longer actively maintained. Using this legacy repository in an educational/reference example is risky because these images do not receive necessary updates or CVE security patches. Users copying this docker-compose.yml for their own projects will unknowingly deploy an unmaintained database cluster.
Proposed Solution
I suggest switching to soldevelo/postgresql-repmgr.
This image is a free, actively maintained, and fully open-source drop-in replacement.
Crucially, it is perfectly compatible with your current example:
- It preserves the exact same environment variables,
repmgrlogic, and internal paths. - Your Docker Compose setup will continue to work immediately without any structural changes, but it will be backed by a secure, actively supported image.
(Note: SolDevelo maintains a growing library of open-source, Bitnami-compatible images to help the community move away from deprecated or paywalled artifacts. You can find the source code and other images here: https://github.com/SolDevelo/containers)
Suggested Changes in running_pg_cluster_in_docker/1. Hello Postgres cluster/docker-compose.yml:
# Old
container_name: postgres_1
image: docker.io/bitnamilegacy/postgresql-repmgr:17.6.0
...
container_name: postgres_2
image: docker.io/bitnamilegacy/postgresql-repmgr:17.6.0
# New
container_name: postgres_1
image: docker.io/soldevelo/postgresql-repmgr:17.6.0
...
container_name: postgres_2
image: docker.io/soldevelo/postgresql-repmgr:17.6.0
I would be happy to submit a Pull Request to update this reference so your example remains robust and follows best security practices. Would you be open to that?
- Dominant language
- No language data
- Stars
- 181
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mfvanek/useful-sql-scripts
-
enhancement good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
enhancement good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in mfvanek/useful-sql-scripts
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenLiberty/open-liberty#35839 ·
-
affects-9.0 found-by-ai may-affects-25.10 may-affects-26.3 may-affects-26.9 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major sig/execution type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
antlr/grammars-v4#5014 · 1 comment ·