-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update PyTorch Image to officially released one #1020
Labels
Comments
If automatic release is not setup, we might have to manually release a build and update it in ksonnet for 0.2 release |
/cc @kunmingg |
Will fix auto-release workflow. |
P0. Because we want this fixed before the next RC cut. |
/assign @kunmingg |
@johnugeorge New image at gcr.io/kubeflow-images-public/pytorch-operator:v20180619-2e19016 |
This was referenced Jun 19, 2018
Merged
yanniszark
pushed a commit
to arrikto/kubeflow
that referenced
this issue
Feb 15, 2021
Signed-off-by: Ce Gao <gaoce@caicloud.io>
surajkota
pushed a commit
to surajkota/kubeflow
that referenced
this issue
Jun 13, 2022
…beflow#1020) * The PR numbers are now 4 digits (XXXX) as a result the worklfow names exceeded the Kubernetes limits and the tests aren't running.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update PytorchImage in https://github.com/kubeflow/kubeflow/blob/master/kubeflow/pytorch-job/prototypes/pytorch-operator.jsonnet#L9 to the one in kubeflow public image repo
The text was updated successfully, but these errors were encountered: