rdmorganiser / rdmorganiser/rdmo-docker-compose
Adjust Docker Infrastructure for PostgreSQL 18.x
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Proposed Changes
Volume Mapping (PostgreSQL 18 Layout)
1- Modify dc_master.yaml to mount the volume at the parent level. This allows the PostgreSQL engine to manage its own internal versioning structure.
From: /var/lib/postgresql/data
To: /var/lib/postgresql
2- Automation
Update the preparation script to ensure the local host directory exists before the container starts, preventing permission mapping issues.
3. Dockerfile.tpl Adjustments
Ensure the system user remapping logic correctly handles the system postgres user while allowing the database engine to start with the environment-defined POSTGRES_USER.
4. Health Check Correction
use the specific user defined in the project configuration:
healthcheck:
test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER}"]
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.
Research direction
Review dc_master.yaml, the preparation script, and Dockerfile.tpl to trace volume creation, user remapping, and PostgreSQL startup. Check the healthcheck configuration against the project’s POSTGRES_USER setting. Done means PostgreSQL 18 starts successfully with the parent-level volume mount, correct permissions and user handling, and a passing readiness check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- database, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100