While we have used the Linux subsystem successfully together with several clients, we do not officially support it at the moment.
With Windows 10, you can fairly easily run code in a Linux environment without the overhead of a virtual machine or installing an emulator.
To first activate and install it on your system, follow these instructions. Please note that you require admin rights on the Windows machine to enable the Linux subsystem.
If you have no specific reason to select another one we recommend to choose Ubuntu 18.04 LTS from the Microsoft store page as Linux distribution. But other Linux distributions should work just as well.
We additionally recommend to install the terminal Cmder, which we find incredibly helpful. This is optional though and you can also launch the Linux subsystem directly from the application panel.
There is virtually no overhead and you are ready to use the terminal as if it was a Linux system.
The Windows file system is mounted as if it was an external hard drive under the
Linux subsystem. E.g., you can find the
Desktop directory here:
Vice versa, you can find the contents of the Linux subsystem home directory here:
We strongly recommend to only transfer files from within the Linux subsystem (either to or from Windows).
You can now continue with installing Salvus.
TLS/SSL connections (e.g. connections over HTTPS) require a few things to work correctly. A simple way to test if everything works is to run for example
in the WSL which should finish without error. In case you encounter SSH connection problems there are a few likely causes:
Anti-Virus software running on the Windows host has been reported to block SSL connections in the WSL.
Executing the following command in the windows powerwhell will print all active anti virus programs:
powershell.exe "Get-CimInstance -Namespace root/SecurityCenter2 -ClassName AntivirusProduct" | grep displayName
Try disabling them temporarily and see if that helps.
This can result in very similar errors. Please see this page for details.