Create shared start/stop scripts for better extensibility#367
Create shared start/stop scripts for better extensibility#367davejrt merged 9 commits intopuppetlabs:masterfrom
Conversation
|
@glorpen can you please resolve the merge conflict here and we can look at getting this merged for the next release. |
davejrt
left a comment
There was a problem hiding this comment.
Can you please remove all detach params and documentation pertaining to this param, as it's being removed.
|
@davejrt Done, I hope I've catched all run::detach uses. |
|
LGTM |
|
@glorpen looks like this is breaking on systems using upstart. Primarily the -a flag with docker start. Do you want to push a fix, or we'll have to revert the PR so it doesn't break our next release. |
|
I think you're correct, can you revert it on your fork and push that as the commits are squashed on the merge of the PR |
|
Done |
|
Do you want to submit the fix as a PR? |
|
If it is required, I'm fine with you just merging/squashing/etc it. |
|
@davejrt not sure if repo silence is caused by holidays or not; let me know if you want me to create that PR after all :) |
|
Happy Holidays, if you could create the PR that would be great |
This PR replaces current docker-runscript with scripts for service start and stop actions - used by systems with and without systemd.
There is not much added functionality for end-user, just singular new parameter -
after_createindocker::run. In my current use case it will allow to easily add connecting container to multiple networks (sincedocker createis now always used).Additionally this PR opens a way to add handling for named user/group from host system, eg.
--user $(id -u user):$(id -g group). (PR's for both will come later)Currently the first one is possible by overusing
extra_systemd_parametersparameter and second one is not even possible because of systemd$()handling.Main changes:
docker createis now always used in init scripts, nodocker run