instructions for Windows

[fdiblen]

We need the instructions below for Windows.

• remote machine at SURF HPC Cloud
• local machine via Docker
• local machine via VirtualBox

Most of the instructions for Linux will probably work but some additional steps or changes may be required.

Links to Linux instructions can be found below.
remote machine at SURF HPC Cloud
local machine via Docker
local machine via VirtualBox

[sverhoeven]

So these are instructions how to install Ansible and run one of the playbooks to install a GH Action runner on a remote server from Windows..

[sverhoeven]

@cwmeijer em me wehere able to get the vagrant setup running on his Windows machine.
There where 2 problems

• Ansible can not run as controller from Windows, so we copied the vagrant private key to wsl and ran ansible from wsl
• wsl permissions the permissions where to open, but chmod go-rw -R . helped

[sverhoeven]

The Windows 10 version 2004 update has been released. This will cause WSL-2 to use Hyper-V and Virtualbox to use very slow Hyper-V compatibility mode. See https://docs.microsoft.com/en-us/windows/wsl/wsl2-faq#will-i-be-able-to-run-wsl-2-and-other-3rd-party-virtualization-tools-such-as-vmware-or-virtualbox .

There is no currently no workaround to have WSL2 and a performant Virtualbox. To have performant Virtualbox you need to disable Hyper-V. To have WSL2 you need Hyper-V enabled.

[sverhoeven]

The vagrant guide for Windows could use a Hyper-V based VM. Windows 10 Home does not have Hyper-V support so only Windows 10 Pro and higher could start the VM.

[sverhoeven]

I switched back to WSL v1 to be able to still have Virtualbox and WSL together.

[cwmeijer]

That explains why I could just run virtualbox with or without hyper-v. In my case the result was slow in both cases. I had expected some error instead when starting a VM when Hyper-V enabled.