Vagrant in WSL unable to access Virtualbox and Windows environment

[r3dy]

Vagrant in WSL unable to access Virtualbox and Windows environment

[R3dy]

I'm not sure about the hyperv call but I think that's just normal Windows behavior.

From your log file I see this looks likely to be the issue

ERROR base: No user Windows access defined for the Windows Subsystem for Linux. This is required for VirtualBox.
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::WSLVirtualBoxWindowsAccessError: Vagrant is unable to use the VirtualBox provider from the Windows Subsystem for
Linux without access to the Windows environment. Enabling this access must be

[sn0x736e]

I resolved this issue by running vagrant using command vagrant up goku

While debugging I found out that environment variables were not available as same as they were set using export because I set environment variables as non-sudo user and was running vagrant with sudo which changed the environment.

a simple workaround of this Problem is to first set proper environment variables then run vagrant up goku or if you want to run as sudo you must use sudo -E vagrant up goku which will preserve the environment variable

Environment with sudo vagrant up goku

Environment with vagrant up goku / sudo -E vagrant up goku