Bringing machine ‘database’ up with ‘virtualbox’ provider…
Bringing machine ‘infrastructure’ up with ‘virtualbox’ provider…
==> database: Checking if box ‘ubuntu/trusty64’ version ‘20190429.0.1’ is up to date…
==> database: Machine already provisioned. Run
vagrant provision or use the
==> database: flag to force provisioning. Provisioners marked to run always will still run.
==> infrastructure: Checking if box ‘centos/7’ version ‘1905.1’ is up to date…
==> infrastructure: Clearing any previously set forwarded ports…
==> infrastructure: Fixed port collision for 22 => 2222. Now on port 2200.
==> infrastructure: Clearing any previously set network interfaces…
==> infrastructure: Preparing network interfaces based on configuration…
infrastructure: Adapter 1: nat
infrastructure: Adapter 2: hostonly
==> infrastructure: Forwarding ports…
infrastructure: 22 (guest) => 2200 (host) (adapter 1)
==> infrastructure: Running ‘pre-boot’ VM customizations…
==> infrastructure: Booting VM…
==> infrastructure: Waiting for machine to boot. This may take a few minutes…
infrastructure: SSH address: 127.0.0.1:2200
infrastructure: SSH username: vagrant
infrastructure: SSH auth method: private key
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,
If the box appears to be booting properly, you may want to increase
the timeout (“config.vm.boot_timeout”) value.
It seems like the infrastructure vm is unable to boot properly, what can I do?