vagrant up fails

[philbelland]

Context: Linkedin course Running Spring Boot in Production, chapter 2

phil@A10 MINGW64 ~/vagrant_amzn2
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'gbailey/amzn2' version '20240829.0.0' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key

VM output in screenshot

[gebailey]

I'm not able to reproduce this. What versions of VirtualBox, vagrant, and the amzn2 box are you using?

[philbelland]

phil@A10 MINGW64 ~/vagrant_amzn2
$ vagrant --version
Vagrant 2.4.3

phil@A10 MINGW64 ~/vagrant_amzn2
$ /c/Program\ Files/Oracle/VirtualBox/VBoxManage.exe -v
7.1.4r165100

I think the amzn2 box version is in the vagrant up command output I pasted above, or else I don't know how to get the version.

This is all from Git Bash.
The "vagrant up" command has the same result from powershell as admin.

[philbelland]

Just realized it may be a conflict between WSL2 and vbox - I activated wsl for the docker part of the course. I'm on windows 10 by the way...

[philbelland]

I tried the same thing in Fedora 41. After much tinkering to get virtualbox properly installed, I got better results.

phil@fedora:~/vagrant_amzn2$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'gbailey/amzn2' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'gbailey/amzn2'
    default: URL: https://vagrantcloud.com/api/v2/vagrant/gbailey/amzn2
==> default: Adding box 'gbailey/amzn2' (v20240829.0.0) for provider: virtualbox (amd64)
    default: Downloading: https://vagrantcloud.com/gbailey/boxes/amzn2/versions/20240829.0.0/providers/virtualbox/amd64/vagrant.box
    default: Calculating and comparing box checksum...
==> default: Successfully added box 'gbailey/amzn2' (v20240829.0.0) for 'virtualbox (amd64)'!
==> default: Importing base box 'gbailey/amzn2'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'gbailey/amzn2' version '20240829.0.0' is up to date...
==> default: Setting the name of the VM: vagrant_amzn2_default_1733345932196_80301
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant
guest is not trusted, you may want to disable this option. For more
information on this option, please refer to the VirtualBox manual:

  https://www.virtualbox.org/manual/ch04.html#sharedfolders

This option can be disabled globally with an environment variable:

  VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

or on a per folder basis within the Vagrantfile:

  config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
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.

VM output