Skip to content
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

Closed
johnugeorge opened this issue Jun 18, 2018 · 6 comments · Fixed by #1034
Closed

Update PyTorch Image to officially released one #1020

johnugeorge opened this issue Jun 18, 2018 · 6 comments · Fixed by #1034

Comments

@johnugeorge
Copy link
Member

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

@johnugeorge
Copy link
Member Author

johnugeorge commented Jun 18, 2018

If automatic release is not setup, we might have to manually release a build and update it in ksonnet for 0.2 release

@johnugeorge
Copy link
Member Author

/cc @kunmingg

@kunmingg
Copy link
Contributor

Will fix auto-release workflow.

@jlewi
Copy link
Contributor

jlewi commented Jun 18, 2018

P0. Because we want this fixed before the next RC cut.

@kunmingg
Copy link
Contributor

/assign @kunmingg

@kunmingg
Copy link
Contributor

@johnugeorge New image at gcr.io/kubeflow-images-public/pytorch-operator:v20180619-2e19016

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants