Closed zlcnju closed 5 years ago
Hi @zlcnju. Thanks for your PR.
I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
add a init container default use busybox image, add wait master running by check dns master addr. And this initcontainer config can be configured in the pytorch configmap. If aggred, I will add the configmap config in the kubeflow project
/ok-to-test
/cc @gaocegege /cc @richardsliu
@johnugeorge @gaocegege any other suggestions?
/lgtm
@zlcnju Thanks for your contribution! :tada: :+1:
@tossmilestone Thanks for your review!
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: richardsliu
The full list of commands accepted by this bot can be found here.
The pull request process is described here
May I ask which release will include this fix? If I use the 0.6 release, will I meet the same problem described in issue#186 ?
Can you use latest 0.7 release
Can you use latest 0.7 release
I use the 0.7.0 image from gcr.io, do this image contain this fix?
Can you use latest 0.7 release
I use the 0.7.0 image from gcr.io, do this image contain this fix?
you can check the pod create by pyjob, If init container exists, this fix included
Can you use latest 0.7 release
I use the 0.7.0 image from gcr.io, do this image contain this fix?
you can check the pod create by pyjob, If init container exists, this fix included
it do contain this fix, thank you very much
use init container for worker pod to wait master pod ready
fix 186