Help talk:MediaWiki-Vagrant in Labs

Good

Thanks for this help page! Worked smoothly:

==> default: Notice: Finished catalog run in 494.92 seconds

I got this, easily resolved by running setup.sh with my user:

Path: /srv/mediawiki-vagrant/Vagrantfile
Line number: 40
Message: RuntimeError: The mediawiki-vagrant plugin hasn't been installed yet. Please run `setup.sh`.

The wiki is working, however I can't ssh into it.

$ vagrant ssh
The provider 'lxc' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.

--Nemo 17:44, 11 September 2015 (UTC)

I don't know what happened, but now it works. :o (I did many MediaWiki configuration changes and run "vagrant provision" a few times, but I don't know how that could matter.) --Nemo 20:07, 12 September 2015 (UTC)

No usable default provider

After running setup.sh manually and trying to run 'vagrant up' I got this:

$ vagrant up
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.

--brion (talk) 18:51, 3 November 2015 (UTC)

Ok this may be due to not having loaded the profile magic that sets the user properly? After a reboot I got different errors (permissions-related on .vagrant dir), presumably because I ran ./setup.sh as myself. After manually chown -R'ing .vagrant to mwvagrant, it seems to be loading up happier. --brion (talk) 18:56, 3 November 2015 (UTC)