-
Notifications
You must be signed in to change notification settings - Fork 539
[Bug] KubeRay seems not to work on minikube on M1 macs. #523
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
Comments
Well...that's no good. Let me try to reproduce that. What happens if you instead use KinD with the default set-up ( |
I'm also surprised by the |
I was not able to reproduce the issue -- we can take a look together at what's going on. |
From our discussion, it looks like it might be specific to Minikube on M1 Macs. |
TODO: Try to use [20220921 Updated] |
[Possible Solution]
|
ray-project/ray#31522 enables users to run Ray in Docker containers on ARM machines (including Mac M1) and on ARM cloud instances (e.g. AWS Graviton). I will try to run KubeRay on Mac M1 with the new images. |
Search before asking
KubeRay Component
ray-operator
What happened + What you expected to happen
I followed the instruction in the document. When I try to deploy the ray cluster with ray-cluster.autoscaler.yaml, both the head node and worker nodes will crash with OOM. Next, I increased both memory limit and memory request configuration for both head and worker, and the nodes will not OOM but containers will still exit with Error as shown in the following figures.
log for head node
Reproduction script
Anything else
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: