Instructions to set up a local Wikidata instance with Vagrant:

1. Get the latest MediaWiki Vagrant code and all its sub-modules (with --recursive):

git clone --recursive https://gerrit.wikimedia.org/r/mediawiki/vagrant mediawiki_vagrant

2. Install & run the default box:

cd mediawiki_vagrant
./setup.sh # Unix
./setup.bat # Windows
vagrant up
vagrant git-update

3. Update the box

vagrant ssh
sudo apt-get update && sudo apt-get upgrade

4. Update the Composer & set a high timeout to avoid T150581:

composer selfupdate --update-keys
composer config --global process-timeout 9600

4. Install & run Wikidata:

vagrant roles enable wikidata
vagrant provision

You can then point your browser to:
http://wikidata.wiki.local.wmftest.net:8080/

and create an item via:
http://wikidata.wiki.local.wmftest.net:8080/wiki/Special:NewItem

Running

vagrant roles enable wikidata
vagrant provision

I raise T146443

vagrant reload

==> default: Checking if box 'debian/contrib-jessie64' is up to date...
Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 8080 is already in use
on the host machine.

To fix this, modify your current project's Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

  config.vm.network :forwarded_port, guest: 8080, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding. You could
try 'vagrant reload' (equivalent of running a halt followed by an up)
so vagrant can attempt to auto-correct this upon booting. Be warned
that any unsaved work might be lost.

I'm trying to figure out which process is listening on port 8080, but running:

lsof -i :8080

I don't get response.

In T167025#3341030, @Afnecors wrote:

vagrant reload

==> default: Checking if box 'debian/contrib-jessie64' is up to date...
Vagrant cannot forward the specified ports on this VM, since they
would collide with some other application that is already listening
on these ports. The forwarded port to 8080 is already in use
on the host machine.

To fix this, modify your current project's Vagrantfile to use another
port. Example, where '1234' would be replaced by a unique host port:

  config.vm.network :forwarded_port, guest: 8080, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this
case, Vagrant was unable to. This is usually because the guest machine
is in a state which doesn't allow modifying port forwarding. You could
try 'vagrant reload' (equivalent of running a halt followed by an up)
so vagrant can attempt to auto-correct this upon booting. Be warned
that any unsaved work might be lost.

I'm trying to figure out which process is listening on port 8080, but running:

lsof -i :8080

I don't get response.

Is this a blocking problem? Couldn't you simply edit the vagrant file to use another port as suggested?

I didn't want to hard code the port in Vagrant file, so I followed the doc adding auto_correct: true.

Then running the last commad vagrant provision I raise T150581.

Uploaded a Vagrant box with the Wikidata role enabled:
vagrant init hjfocs/wikidata; vagrant up --provider virtualbox

In T167025#3318594, @Hjfocs wrote:

You can then point your browser to:
http://wikidata.wiki.local.wmftest.net:8080/

and create an item via:
http://wikidata.wiki.local.wmftest.net:8080/wiki/Special:NewItem

create a property:
http://wikidata.wiki.local.wmftest.net:8080/wiki/Special:NewProperty