I am trying WSL 2, also trying Vagrant on it. I used it in Ubuntu 20.04 and it is working properly, but now i am facing problem here in WSL 2 in Windows 10. My Problem might be about SSH problem on WSL, seems 127.0.0.1:222 cannot connect into the image in Virtual Box. please correct me if my understanding is wrong
Technologies Version Involved
Vagrant File
Vagrant.configure("2") do |config|
config.vm.box = "base"
config.ssh.username = "vagrant"
config.ssh.password = "vagrant"
config.vm.define "laravel_envoy" do |laravel_envoy|
laravel_envoy.vm.hostname = "192.168.12.12"
laravel_envoy.vm.box = "bento/ubuntu-18.04"
laravel_envoy.vm.network :private_network, ip: "192.168.12.12"
laravel_envoy.vm.provider "virtualbox" do |bionicv|
bionicv.memory = 4096
bionicv.cpus = 4
bionicv.customize ["modifyvm", :id, "--uartmode1", "disconnected"]
end
laravel_envoy.vm.synced_folder "/mnt/c/Users/jjmigz-win10/Code/gcp-home","/home/vagrant/Code/gcp-home"
end
config.vm.network "forwarded_port", guest: 8992, host: 8991, host_ip: "127.0.0.1"
end
Error Raw Text
jmigzwsl@jmigzw10:/mnt/c/Users/jjmigz-win10/Code/laravel_gitlab_ci_cd_with_envoy$ vagrant up
Bringing machine 'laravel_envoy' up with 'virtualbox' provider...
==> laravel_envoy: Clearing any previously set forwarded ports...
==> laravel_envoy: Clearing any previously set network interfaces...
==> laravel_envoy: Preparing network interfaces based on configuration...
laravel_envoy: Adapter 1: nat
laravel_envoy: Adapter 2: hostonly
==> laravel_envoy: Forwarding ports...
laravel_envoy: 8992 (guest) => 8991 (host) (adapter 1)
laravel_envoy: 22 (guest) => 2222 (host) (adapter 1)
==> laravel_envoy: Running 'pre-boot' VM customizations...
==> laravel_envoy: Booting VM...
==> laravel_envoy: Waiting for machine to boot. This may take a few minutes...
laravel_envoy: SSH address: 127.0.0.1:2222
laravel_envoy: SSH username: vagrant
laravel_envoy: SSH auth method: password
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
laravel_envoy: Warning: Connection refused. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
~/.bashrc config
export VAGRANT_WSL_ENABLE_WINDOWS_ACCESS="1"
export PATH="$PATH:/mnt/c/Program Files/Oracle/VirtualBox"
export VAGRANT_WSL_WINDOWS_ACCESS_USER_HOME_PATH="/mnt/c/Users/jjmigz-win10/Code/laravel_gitlab_ci_cd_with_envoy"
What I tried
i tried to change my host_ip: "127.0.0.1" into my Vagrantfile but still i got error, also I cannot find real solution like this problem using WSL 2 in the internet.
i tried to add this config.vm.boot_timeout
in the Vagrantfile
but still got error
i tried to add this bionicv.gui = true
in my Vagrantfile
but still got error
Related Question - outdated and not using WSL 2
Vagrant Warning: Connection refused. Retrying
Vagrant stuck connection timeout retrying
Vagrant InstallationVagrant must be installed within the Linux distribution used with WSL. While the vagrant.exe executable provided by the Vagrant Windows installation is accessible from within the WSL, it will not function as expected.
Will I be able to run WSL 2 and other 3rd party virtualization tools such as VMware, or VirtualBox? Some 3rd party applications cannot work when Hyper-V is in use, which means they will not be able to run when WSL 2 is enabled, such as VMware and VirtualBox.
Simply CMD-SHIFT-P then "Remote-SSH: Connect to Host..." and the ssh . config entry you just added is automatically listed - you simply select it and voila, vscode connects to your remote vagrant vm!
A bit of monkey patching and here you go.
Just install the plugin vagrant plugin install virtualbox_WSL2
and vagrant ssh
works from WSL2.
Source code: https://github.com/Karandash8/virtualbox_WSL2
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With