Vangrant Up gives me an error :bsdtar: Error opening archive: Failed to open

[Alfred]

Vangrant Up gives me an error :bsdtar: Error opening archive: Failed to open '/Users/Alff/.vagrant.d/tmp/box1405df66cbe219b0bf6355bc3d60361a8376b6b4'

What should I do?

[om...@hipo.biz]

Hi I have the same problem I think it looks like the box with a given hash couldn't created. Have you solved that problem

[Alvaro Miranda Aguilera]

Hello omer

In the past were issues with a version of tar (binary) on Windows, but
that is long gone.

Can you confirm what's the OS in your host?

And what's the vagrant version?

vagrant version

If you can provide a Vagrantfile and copy/paste errors, we can have a look

Thanks
Alvaro.

> --
> 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 vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/b50cbe32-7433-4cd3-a86b-dc810c6798b7%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[dragon788]

Typically when I see this error anymore its due to the host filesystem running out of space. The .vagrant.d folder is on C:\Users\$USERNAME\ (Windows) or /home/$USERNAME/ (Linux) and even if you have your Vagrantfile on D: or E: it will stage a copy of each box in the .vagrant.d folder to clone out to wherever your Vagrantfile is. If you do a 'vagrant box list' you may see other boxes you have tried, and if you don't clean them out using 'vagrant box remove <boxname>' then they will occupy a portion of your disk.