Command 'vagrant up' fails with 'Error: Vagrant failed to initialize at a very early stage'
ottok opened this issue · 4 comments
I've seen at least one Virtualbox 5.2 and Vagrant 2.x user on Mac OS X and one on Windows encounter this error message. I did not learn what the reason was, or how it was fixed.
Filing this in case somebody can reproduce the issue and report here more info.
One reported reason was that the wordpress project was checked out in a path that had umlauts (åäö characters) and Vagrant didn't recover from that.
Another reason was that there was some permission issues, that were bypassed by running sudo vagrant up or on Windows in Administrator PowerShell vagrant up. The root cause of permission issues is however still unknown.
Hello.
I'm having this issue wit OSX 10.15.1. When I run command vagrant up I get the following error
There was an error while executing VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["import", "-n", "/Users/janitaiminen/.vagrant.d/boxes/seravo-VAGRANTSLASH-wordpress/20200130.0.0/virtualbox/box.ovf"]
Stderr: 0%...
Progress state: E_ACCESSDENIED
VBoxManage: error: Appliance read failed
VBoxManage: error: Failed to open OVF file '/Users/janitaiminen/.vagrant.d/boxes/seravo-VAGRANTSLASH-wordpress/20200130.0.0/virtualbox/box.ovf' (VERR_ACCESS_DENIED)
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg *)" at line 307 of file VBoxManageAppliance.cpp`
My Vagrant version is 2.2.9 and VirtualBox version is 5.2.26
It is some sort of permission problem but so far I haven't been able to solve it. Everything works just fine if I run the vagrant commands as sudo
One symptom on the Windows machine I studied was that it ended up installing Vagrant files in C:\Windows\Temp and that it did install plugins, but then immediately after complained that the plugins don't work and need to be "repaired" (but repair command didn't work either).
Please comment if this is still an issue with latest Seravo/WordPress Vagrant box releases.