Wikimedia Developer Support

Any success for Mediawiki-Vagrant on GCP instances?

vagrant
debugging
gcp

#1

What I tried

taven@wiki-debug:~/vagrant$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'debian/contrib-stretch64' version '9.6.0' is up to date...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   default: Adapter 1: nat
   default: Adapter 2: hostonly
==> default: Forwarding ports...
   default: 8080 (guest) => 8080 (host) (adapter 1)
   default: 443 (guest) => 4430 (host) (adapter 1)
   default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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
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.

When enabling vb.gui I see something similiar to this in VirtualBox:

Instance Specs

The instance has nested virtualization enabled and it’s full specs can be seen below in the log file.

Vagrant Config Values

Output of varant config --list

Notes:

  • This was tested with upto 6 gigs of ram for vagrant_ram