docker-library / docker-library/drupal
The bad situation with bind volumes
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 291
- Forks
- 199
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 1
Description
Drupal is really cool but the docker image has an issue where it makes it really annoying to host using docker images, bind volumes. For example a lot of us just create a docker compose with bind volumes to our data and start the app but due to the (bad) design choice of Drupal's dockerfile the volume location has already data which are getting replaced by docker. The solution is as simple as storing the data on a template location and copy them just before the web server starts. I would really like to see this implemented as it would make self hosting Drupal with docker extremely easy.
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
Read the Drupal Dockerfile first, then trace how the image prepares its data before the web server starts. Reproduce the issue with a Docker Compose bind-volume setup and verify that a fresh mounted location receives the image data without replacing existing user data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100