pre_start/init-Containers should support own/overwritten Volumes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.2k
- Forks
- 5.8k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 55
Description
Description
Hi,
i appreciate the feature of pre_start/Init-Containers. That is really cool and solves many things, where we built own solutions with startup-scripts and stuff...
But i miss a thing in it:
The configuration as far as i can see currently does not support volumes for the pre_start-Container. It should.
And: I have volumes mounted readonly to my service (https-Certificates and stuff), which the init-Container should be able to write. It would by nice to
- be able to define ADDITONAL volumes
- be able to overwrite/change "base-service"-volumes
I am sorry, i am not able to do a pullrequest, "go" is not my language and i am not into compose-codewise.
Thanks a lot in advance!
Best regards
Stefan
PS: I partly mentioned that in my reply to the pre_start-pull-request here: https://github.com/docker/compose/pull/13862#issuecomment-4887343263
Contributor guide
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
Start by reviewing the pre_start/Init-Containers configuration and the referenced pull request #13862. Trace how volumes are currently handled for the base service and init container; done means supporting additional volumes and allowing base-service volumes to be overwritten or changed for the init container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100