Replies: 1 comment 1 reply
-
|
Any insights? 😢 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
the scaling approach of daft via ray at first appears very promising to me.
Before going to kubernetes I'd thought playing with a docker-compose based setup should be a faster start.
So I wrote a little compose yaml:
A tiny Dockerfile:
and an associated script, essentially
daft_ray_test.py:I played a lot with ray options, runner-adresses etc. but didn't get things to work.
The closest (I think) I got is the attached configuration, which produces the following error though:
At the same time the logs of head+worker look ok and the ray dashboard also shows that the worker(s) has successfully connected to the head.
Is there anything obvious I'm missing?
Beta Was this translation helpful? Give feedback.
All reactions