-
Notifications
You must be signed in to change notification settings - Fork 37
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
Cannot install runhouse on static cluster #1166
Comments
I have a temporary solution which is manually creating the env and starting the runhouse server on the machine - is that the way to go? Also: is it possible to have multiple ssh creds, one for each ip address in the cluster if I pass in a list? |
Hey Adit thanks for reaching out! You can create an env and send it to the cluster independently, or create it as part of sending the function to the cluster in the We have some more general info on Envs here. For the example provided you could do something like:
Let us know if this helps. As for SSH creds, we don’t currently support multiple SSH creds for the |
Hi @jlewitt1, thanks for the response! Regarding the env, I'm referring not to the runhouse concept of an env, but rather the python env in which the runhouse package is originally installed. When I tried to initialize a local ubuntu machine as a cluster, it tried to use the base pip (not in any virtual environment). Check out PEP 668, new versions of Ubuntu don't allow package installs on the base pip which is why this error is happening (see my traceback as well as https://www.omgubuntu.co.uk/2023/04/pip-install-error-externally-managed-environment-fix) Yes, the use case is mainly that different clusters might have different usernames. The credentials is an easy fix since I can just use an SSH key. Would it be difficult to support a list of credentials that is the same length as the list of IPs, rather than just one? Regarding the Env or CondaEnv, I ran into an install issue due to what seems like a bug in the code, see #1167. Appreciate your help! |
Gotcha ok thx for clarifying - we've actually talked about adding virtualenv or pyenv as additional Runhouse supported env types, but until then manually creating the env as you did sounds like the best way around that. For supporting a list of creds, that's probably something we could support, do you currently have multiple VMs that you are trying to string together? curious to hear more about the use case Also we're pushing a fix to the condaEnv issue shortly, thx for flagging! |
Appreciate it! The use-case for the multiple credentials is we want to make an ad-hoc cluster out of on-prem machines, and possibly scale up to cloud VMs as well, and these may have different creds. |
Makes sense, that's also something we've talked about - assuming all the clusters are in the same VPC we could probably support that, otherwise would require a bit of hoop jumping to allow each of the worker nodes to communicate with the head node. Happy to keep you posted on the timing of that feature! Also the conda issue is now fixed, you can install from main if that's a blocker for now until the next release |
I have an Ubuntu (24.04 - LTS) machine on my local network that I would like to use as a run.house cluster. Here's a minimal snippet to reproduce:
However, I get the following error
Logs + traceback
My understanding is it trying to use the base python, but Ubuntu is not letting it do a pip install in the base python environment. How can I tell it to use a virtual environment? Don't see any docs for this.
The text was updated successfully, but these errors were encountered: