The problem is, that the network interface attached to WSL2 cannot see the localhost ip address which prevents vagrant ssh from working. There is well known issue related to networking when WSL2 is used. export VAGRANT_WSL_WINDOWS_ACCESS_USER_HOME_PATH='/mnt/c/TestDir'.Optional: If the base folder is in another location than your home directory, set it accordingly in order to make stuff like vagrant ssh work.adds the location of virtualbox within WSL2 to the path variable.Required: export PATH='$PATH:/mnt/c/Program Files/Oracle/VirtualBox'.ensures that vagrant within WSL can access the windows resources, like VirtualBox.Required: export VAGRANT_WSL_ENABLE_WINDOWS_ACCESS='1'.To access windows resources outside the WSL2 distro, you have to set the following environment variable inside your WSL2 distro: Follow the instructions in order to install Vagrant in your WSL2 distro accordingly.

Use an ssh key with correct permissions set for ansible (see SSH Keys)įirst of all it is recommended to take a quick look into this guide which explains how WSL2 can be used to run vagrant within the WSL2 distro while actually working with the windows host components.

Configure networking (see Networking) between WSL2 and Host.

Install and configure ansible in the WSL2 distro.

Install vagrant within the WSL2 distro (see Basics).

Install a WSL2 distribution (I've used ubuntu).Setup and configure WSL2 on your Windows System.In general, you have to perform the following steps which will be explained in detail down below: This goal can be achived by leveraging the sharing-functionalities between the WSL2 and the windows host os. This small guide aims to help all fellow windows users out there, who use VirtualBox on the windows-host-os but want to work with vagrant+ansible smoothly. Use vagrant and ansible to provision your VirtualBox-VMs on Windows

How to use virtualbox on l