-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CHE-3686: fix docker machines addresses setting #3812
Conversation
@amisevsk Please take a look too |
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.
launcher changes are not required as support has been dropped.
Set internal machine address by CLI from CHE_IP. Add and fix docs in che.env. Change behavior of default machine server address evaluation to be similar to the previous state. Code cleanup. Signed-off-by: Alexander Garagatyi <[email protected]>
thanks |
@benoitf Thanks, I rebased this PR to resolve conflicts |
This issue has recently come up. And it should not be the situation where setting this by a user is required. Does this branch fix this issue? https://github.com/codenvy/che-docs/issues/75#issuecomment-273801117 |
@TylerJewell yes, I think this PR will solve that issue. |
@garagatyi LGTM. Thanks for cleaning up my code. As long as the launcher/CLI sets |
Build success. https://ci.codenvycorp.com/job/che-pullrequests-build/1693/ |
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 would like some time to review the modifications to Che.env, verify the networking docs and also have someone verify that they can start a new server on digital ocean by only setting Che host.
@amisevsk It really depends on how che-server is launched and how CLI works(in case of launching using CLI). There is no guaranty that CLI will always set this property or that other vendor will not embed che-server without usage of CLI. |
@garagatyi - this is ok to merge. We hvae had multiple people run into these issues and have had to set CHE_DOCKER_EXTERNAL_* variables temporarily. Would you advise that we merge this in time for 5.1.2, a bug fix release for Monday? |
Yes, I think we can merge it. Should I merge it now? |
Yes, please - we should then do some tests on nightly on digital ocean tomorrow to verify that che starts easily with only CHE_HOST. |
ok, I'm merging this PR and dependent in Codenvy. Roman will be able to cherry pick into bug fix branch if needed. |
What does this PR do?
Set internal machine address by CLI from CHE_IP.
Add and fix docs in che.env.
Change behavior of default machine server address evaluation
to be similar to the previous state.
Code cleanup.
What issues does this PR fix or reference?
Final addition to fix of #3686
Tests written?
Yes
Changelog
Fix docker machines addresses setting