Here's the full text of the command and the error. Note that the
"Greg-Intermaggio-X1-Greg-Intermaggio" directory doesn't exist in
"C:\ProgramData/HashiCorp/VagrantVMware/"-- the only thing there is the
"GREG-INTERMAGGI-Greg Intermaggio" directory, which has a UserData
directory but appears to be missing the helper.args file, and which may be
missing additional files (I don't know what to look for).
C:\WINDOWS\system32>vagrant box add laravel/homestead
C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/sudo_helper.rb:156:in
`initialize': No such file or directory @ rb_sysopen -
C:\ProgramData/HashiCorp/VagrantVMware/Greg-Intermaggio-X1-Greg
Intermaggio/UserData/helper.args (Errno::ENOENT)
from C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/sudo_helper.rb:156:in
`open'
from C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/sudo_helper.rb:156:in
`with_args_file'
from C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/sudo_helper.rb:115:in
`execute'
from C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/sudo_helper.rb:103:in
`call'
from C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/sudo_helper.rb:39:in
`call'
from C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/sudo_helper.rb:77:in
`installed?'
from C:/Users/Greg
Intermaggio/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-5.0.1/lib/vagrant-vmware-workstation/plugin.rb:28:in
`call'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/warden.rb:34:in
`call'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/builder.rb:116:in
`call'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/runner.rb:66:in
`block in run'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/util/busy.rb:19:in
`busy'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/action/runner.rb:66:in
`run'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/environment.rb:543:in
`hook'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/lib/vagrant/environment.rb:194:in
`initialize'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/bin/vagrant:118:in
`new'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.0/bin/vagrant:118:in
`<main>'
On Wednesday, November 1, 2017 at 11:08:17 PM UTC-7, [email protected]
wrote:
>
> Hi, I'm trying to install the vagrant vmware workstation plugin as well as
> the laravel/homestead box on my 64 bit windows 10 machine. I'm running into
> an error, however, because it looks like the paths are not being generated
> and selected correctly.
>
> Specifically, this is the path that is being generated when I install the
> plugin: C:\ProgramData\HashiCorp\VagrantVMware\GREG-INTERMAGGI-Greg
> Intermaggio
>
> And this is the path that it's looking for when I try to install the box:
> C:\ProgramData/HashiCorp/VagrantVMware/Greg-Intermaggio-X1-Greg Intermaggio
>
> Any ideas on how to fix this?
>
>
> Thank you for your help!
>
> -Greg
>
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/4529b322-1ff3-4884-b685-bac8a89ea4f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
