-
Notifications
You must be signed in to change notification settings - Fork 888
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
Support for the aarch64 arm64 architecture #2745
Comments
Please try with Kubeflow 1.9 https://github.com/kubeflow/manifests/commits/v1.9-branch or the master branch |
Merged #2659 into this issue |
@yashprakashsharma you need to retry with the 1.9 release and post your findings here, not in slack. |
Hi @juliusvonkohout, I already migrated to x86_64 architecture, and I am using v1.8.1 it works fine, I no longer have access to a arm64 machine to try v1.9. I will give it a try whenever I get access to arm64 machine |
Well if anyone finds any images not available for arm64 in the Kubeflow 1.9 branch please post them here. |
KFP does still not run on arm64: kubeflow/pipelines#10309 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/lifecycle frozen |
Validation Checklist
Version
1.8
Describe your issue
kubeflow ran on my old x86_64 architecture linux instance but using same method for a new instance with aarch64(arm64) arch multiple pods ceash cause containers in them fail continuously on researching further i found images for failing container were not supporting arm64 arch.
Images for reference can be found here:
https://kubeflow.slack.com/archives/C7REE0ETX/p1717502674581769
Steps to reproduce the issue
kubeflow manifest v1.8.0 installation on aarch64
Put here any screenshots or videos (optional)
https://kubeflow.slack.com/archives/C7REE0ETX/p1717502674581769
The text was updated successfully, but these errors were encountered: