You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users want to test KubeRay locally on M1 Mac, but it fails with unhelpful error messages, e.g. Raylet is considered dead.
At a minimum, we should
Detect that we're on M1 and print a helpful error message
Mention this prominently in the docs (I didn't see any such mention and I was looking for it)
UPDATE: Actually, it works if you use the -aarch64 in the image name. We should add this to the documentation, and investigate if it's possible to automatically use the correct image (since otherwise users have to manually edit any sample YAML that they want to try)
The text was updated successfully, but these errors were encountered:
@architkulkarni I have had no problems with the -aarch64 ray images on M1 MackBook pro. I do use rancher desktop with kind. Perhaps documenting that might a good / better option.
Also adding support for the that architecture for the kuberay images might not be a bad thing. There's a PR for this already: #1442.
Thanks! I can also confirm that adding the tag -aarch64 makes it work. I'll leave this issue open to track improving the documentation, because I don't think it'll be obvious to users and right now there's no clear error message.
architkulkarni
changed the title
KubeRay does not support M1 Mac
[Doc] Add instructions to use -aarch64 tag for images for M1 Mac in KubeRay YAMLs
Oct 26, 2023
Some users want to test KubeRay locally on M1 Mac, but it fails with unhelpful error messages, e.g.
Raylet is considered dead
.At a minimum, we should
UPDATE: Actually, it works if you use the
-aarch64
in the image name. We should add this to the documentation, and investigate if it's possible to automatically use the correct image (since otherwise users have to manually edit any sample YAML that they want to try)The text was updated successfully, but these errors were encountered: