While trying to set up wordpress locally, I noticed that command vagrant -v is broken. Installing both Vagrant from repository and VirtualBox with instructions from wiki, Vagrant throws an error after command 'vagrant up' in local-vagrant folder. Full tutorial - ( https://make.wordpress.org/core/handbook/tutorials/installing-a-local-server/installing-vvv/ ).
vagrant -v throws this message:
/usr/lib/vagrant/version.rb:5:in `read': No such file or directory @ rb_sysopen - /usr/version.txt (Errno::ENOENT) from /usr/lib/vagrant/version.rb:5:in `<module:Vagrant>' from /usr/lib/vagrant/version.rb:1:in `<top (required)>' from /usr/bin/vagrant:18:in `require_relative' from /usr/bin/vagrant:18:in `<main>'
...and vagrant up inside vagrant-local folder throws this:
Bringing machine 'default' up with 'virtualbox' provider... ==> default: Box 'ubuntu/trusty64' could not be found. Attempting to find and install... default: Box Provider: virtualbox default: Box Version: >= 0 The box 'ubuntu/trusty64' could not be found or could not be accessed in the remote catalog. If this is a private box on HashiCorp's Atlas, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: ["https://atlas.hashicorp.com/ubuntu/trusty64"] Error: error setting certificate verify locations: CAfile: /home/daniel/vagrant-local/cacert.pem CApath: none
Alright, I found out that I had to add sudo before the command vagrant up. Everything seemd to set up nicely, but I still can't connect to local.wordpress.dev.
I noticed aswell that, if I now try to use command vagrant up without an sudo, then I get this message:
The VirtualBox VM was created with a user that doesn't match the current user running Vagrant. VirtualBox requires that the same user be used to manage the VM that was created. Please re-run Vagrant with that user. This is not a Vagrant issue. The UID used to create the VM was: 0 Your UID is: 1000