Open Ericxgao opened 1 year ago
I believe it's OK to pass a runtime env to an actor, but according to the error message, you should not try to pass an absolute pathname for the current working directory. Other options (like a remote URI for the directory or pip packages) should be OK. Probably this is because uploading the absolute pathname will be expensive and might vary depending on which node the actor is placed on.
Does it work for you use case if you don't pass in the runtime env?
What happened + What you expected to happen
Trying to initialize an actor with a specified working directory in the
runtime_env
params errors out with:ValueError: . is not a valid URI. Passing directories or modules to be dynamically uploaded is only supported at the job level (i.e., passed to
ray.init)
Initialized as:
balancer = LoadBalancer.options(runtime_env={"working_dir": "."}).remote(2)
Confused on why this is complaining when the behavior is documented here? https://docs.ray.io/en/latest/ray-core/handling-dependencies.html#specifying-a-runtime-environment-per-task-or-per-actor
Versions / Dependencies
Ray[default] @ 2.1.0
Reproduction script
Issue Severity
Medium: It is a significant difficulty but I can work around it.