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: #13862 (comment)
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
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: #13862 (comment)