-
Notifications
You must be signed in to change notification settings - Fork 13
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
milatools setup for Windows #19
Comments
After the above steps, when I run:
Is there any recommendation to solve this? Thank you! |
Same thing happens when I try to WSL2 in Win11
|
Hello, I have the same issue, have you been able to solve it? |
For anyone seeing this, this should now be solved with #65 |
Hello,
I've been having some issues getting VS code's debugger to run on a compute node from my Windows laptop.
How to reproduce the issue:
At least in my case, the
mila init
command hangs after displaying theYour public key does not appear be registered on the cluster. Register it? [Y/n]
message.The workaround:
First you need to successfully run
mila init
to complete your cluster SSH setup.4.1 Download the Anaconda linux setup script from here. For example:
wget https://repo.anaconda.com/archive/Anaconda3-2022.05-Linux-x86_64.sh
4.2 Install Anaconda. For example:
bash Anaconda3-2022.05-Linux-x86_64.sh
Answer yes to the following question: Do you wish the installer to initialize Anaconda3 by running conda init? [yes|no]
4.3 Launch a new Ubuntu terminal from Windows Start menu and confirm that the default Python’s version is now >= 3.8 (this is a milatools requirement) by executing the following command:
python -V
Then you need to generate a public RSA key on your Windows host and add it to the list of authorized keys on the cluster:
pip install milatools
WARNING: The script mila.exe is installed in 'C:\Users\[USERNAME]\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\Scripts' which is not on PATH.
Take in note the absolute path of milatools’ installation foldermila init
5.1 Due to a bug, the
mila init
command will hang after displaying the following message:Your public key does not appear be registered on the cluster. Register it? [Y/n]
type $env:USERPROFILE\.ssh\id_rsa.pub
ssh mila
~/.ssh/authorized_keys
file on Mila’s cluster’s hostSetup is done!
Now you can use the following procedure to launch VS code using a compute node from Mila’s cluster as as development environment:
salloc --cpus-per-task 1 --gres gpu:0 --time=0-1:00:00
Lead to a bugfix:
The problem seems to come from trying to execute the
ssh-copy-id
command on a Windows host (this command does not exist on Windows).I found a one liner that is supposed to be Windows' equivalent of
ssh-copy-id
, but that also hanged on me and I haven't had time to investigate further yet.I will try to find some bandwidth to come up with a bugfix PR in the next few days.
Hopefully the workaround above will save some people some time in the meanwhile.
The text was updated successfully, but these errors were encountered: