Installing via uv breaks dashboard

Dashboard, Monitoring & Debugging
1

It seems like installing ray via uv (instead of pip install) break the dashboard?

1. Severity of the issue: (select one)
None: I’m just curious or want clarification.
Low: Annoying but doesn’t hinder my work.
Medium: Significantly affects my productivity but can find a workaround.

2. Environment:

  • Ray version: 2.46
  • Python version: Python 3.12+
  • OS: ubuntu
  • Cloud/Infrastructure: AWS

3. Repro steps / sample code: (optional, but helps a lot!)
uv init .
uv add ray[default,serve]
uv run ray start --head --dashboard-host=0.0.0.0

4. What happened vs. what you expected:

  • Expected: dashboard should be accessible on 0.0.0.0:8265
  • Actual: it is not accessible.

additional information, from logs: (dashboard exits with segfault)
is this related?

[2025-06-06 01:14:12,039 E 3616 3664] (raylet) agent_manager.cc:87: The raylet exited immediately because one Ray agent failed, a>
The raylet fate shares with the agent. This can happen because

  • The version of grpcio doesn’t follow Ray’s requirement. Agent can segfault with the incorrect grpcio version. Check the grp>
  • The agent failed to start because of unexpected error or port conflict. Read the log `cat /tmp/ray/session_latest/logs/{dashboa>
  • The agent is killed by the OS (e.g., out of memory).
Fail to ray.init on Apple M3 Pro
2

On my version ray 2.44.1 with uv 0.8.5 and python 3.11.13 everything, including your command, runs without issues. Have you checked the suggestions from the ray logs you’ve provided? My grpcio version is 1.71.0.