Page MenuHomeSolus

Can't launch VVV.
Open, LowPublic

Description

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/ ).

Event Timeline

Rayzak triaged this task as High priority.Oct 20 2016, 9:57 AM
Rayzak created this task.
Rayzak added a project: Software.
JoshStrobl raised the priority of this task from High to Needs Triage.Oct 20 2016, 9:59 AM
JoshStrobl added a subscriber: JoshStrobl.

First off, don't change priority.

Secondly, some actual error logs would be helpful.

Sorry.
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
JoshStrobl moved this task from Backlog to Package Fixes on the Software board.Oct 28 2016, 8:39 PM
K4rlos triaged this task as Normal priority.May 16 2018, 7:57 AM
K4rlos moved this task from Package Fixes to Improvement on the Software board.
K4rlos raised the priority of this task from Normal to High.May 16 2018, 8:00 AM
K4rlos added a subscriber: K4rlos.

shit, I missclicked smth on workboard (I don't even know if I should be able to go there). Don't really know how to repair it. Sorry :(((

K4rlos moved this task from Improvement to Package Fixes on the Software board.May 16 2018, 8:05 AM
Sethox raised the priority of this task from High to Needs Triage.EditedMay 16 2018, 9:19 AM
Sethox added subscribers: JoshDobbin, Sethox.

I put the Priority to "Needs Triage" only because @JoshDobbin put it there before it was changed to Normal and High by @K4rlos.

K4rlos removed a subscriber: K4rlos.Aug 7 2018, 10:55 PM
DataDrake triaged this task as Low priority.Oct 16 2018, 5:14 PM