mila code /full/path/to/remote/code does not work properly when launched from WSL Ubuntu on Windows 11 about milatools HOT 5 CLOSED

I've found a solution, thanks to this issue #19

• In windows terminal (cmd, NOT wsl), generate a rsa key in cmd, and place your public key on the mila cluster. You can also do this for wsl separately, but you won't be using this for the mila code command.
• If required, install python using the Microsoft Store (likely other methods work, just haven't tried).
• Run pip install milatools in cmd to install it on the windows side.
• Add the location of milatools and vscode to your Windows Path following this guide.
• For reference, the paths I needed to add were:
  • C:\Users\Joseph Viviano\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0
  • C:\Users\Joseph Viviano\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\Scripts
  • C:\Users\Joseph Viviano\AppData\Local\Programs\Microsoft VS Code\bin.
• Save all entries, and restart your windows terminal (completely close and relaunch, do not try to open a new cmd tab!!!).
• Now, mila code will work in cmd, but it will not be able to launch code (I don't understand why). To resolve this, you must run mila code path/to/remote/folder from an Administrator instance of cmd.

So when all is said and done, you simply launch cmd as an admin, then run mila code <path>, and you can run your remote vscode instance on the mila cluster from Windows 11.

from milatools.

Yes -- this does not work, it produces the behaviour in the first post. I've now successfully performed the second post on two different Windows machines successfully.

from milatools.

I doubt it will ever work on WSL - it's a win11 limitation I think - It's worth reproducing the effort on the cmd side.

from milatools.

Hey @josephdviviano , did you try running mila init inside the WSL shell, to setup your ssh config?

from milatools.

I've found a solution, thanks to this issue #19

• In windows terminal (cmd, NOT wsl), generate a rsa key in cmd, and place your public key on the mila cluster. You can also do this for wsl separately, but you won't be using this for the mila code command.

• If required, install python using the Microsoft Store (likely other methods work, just haven't tried).

• Run pip install milatools in cmd to install it on the windows side.

• Add the location of milatools and vscode to your Windows Path following this guide.

• For reference, the paths I needed to add were:

  • C:\Users\Joseph Viviano\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0
  • C:\Users\Joseph Viviano\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\Scripts
  • C:\Users\Joseph Viviano\AppData\Local\Programs\Microsoft VS Code\bin.

• Save all entries, and restart your windows terminal (completely close and relaunch, do not try to open a new cmd tab!!!).

• Now, mila code will work in cmd, but it will not be able to launch code (I don't understand why). To resolve this, you must run mila code path/to/remote/folder from an Administrator instance of cmd.

So when all is said and done, you simply launch cmd as an admin, then run mila code <path>, and you can run your remote vscode instance on the mila cluster from Windows 11.

@josephdviviano thanks for this. Have you been able to find a workaround to make this work with WSL? Your setup is based on CMD, and I have set up everything on WSL already.

from milatools.