Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for contributing!
I thinks this won't have the desired effect as we are rebooting the instance right after:
ansible-elastic-cloud-enterprise/tasks/direct-install/main.yml
Line 5 in 0624ea5
Having docker daemon enabled should be enough. However, if docker takes too long to start or fails to start (conf problem for example) it might be interesting to ensure that docker is up right before running the actual ECE install.
Moving this current piece of code right before this line might be what we need:
ansible-elastic-cloud-enterprise/tasks/ece-bootstrap/main.yml
Line 21 in 0624ea5
Also, if anyone want to use this playbook to only bootstrap ECE (tag
bootstrap
), i.e. on a machine which was already provisioned (docker installed, configured) , that also might be interesting to ensure docker is up before starting the actual install of ECE.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like your suggestion for the alternative location for the docker start task, I'll go ahead and test that change in my environment, just to make sure it functions as intended!