vagrant adding box problem

[Michael Legleux]

I packaged a windows 7 box using vagrant 1.6.5 on windows 8.1 and have been using it successfully for awhile on the same machine.

I just moved the .box to a few other machines (windows 8.1 and ubuntu12.04) and when adding the box I get the error:

The box failed to unpackage properly. Please verify that the box

file you're trying to add is not corrupted and try again. The

output from attempting to unpackage (if any):

x ./box-disk1.vmdk: truncated gzip input

bsdtar.EXE: Error exit delayed from previous errors.

[Alvaro Miranda Aguilera]

hello Michael,

I can't remember the specific version, but in some of Vagrant windows
installer was a bsdtar

the workaround 1 was to delete and reinstall
fix was delete and install the latest one

1.7.2 is pretty stable if you want to give it a shot.

Alvaro.

> --
> 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.
> For more options, visit https://groups.google.com/d/optout.

[Michael Legleux]

Thanks a lot Alvaro, I am in the process of installing 1.7.2 for windows.

I did see that it was using bsdtar during packaging.

Does 1.7 use a different compression utility or just a different version.

The strange thing is that the process works fine on the one windows 8 machine but any other machine with different vagrant versions, it doesn't like it.

Will report back if the same thing occurs in 1.7.2. after the long packaging process.

[Michael Legleux]

Unfortunately I got the exact same error using Vagrant 1.7.2.

[Michael Legleux]

Could this be possibly related to the commands vagrant is using being 32bit while the file i'm trying to package is greater than 4GB?

On Thursday, May 21, 2015 at 12:32:35 PM UTC-7, Michael Legleux wrote:

[dragon788]

The 4GB file size would only matter if you were on a FAT32 filesystem. As long as you are on NTFS the file size shouldn't matter. What is more likely is that you need to run vagrant box --package yourboxname to export the box as you've been using it over to a new system.

[Michael Legleux]

While your first statement seems logical, the second statement you suggest is exactly what I've been doing. 

The problem is, when I bring it to the new system from windows 8(which in this case was ubuntu AND windows 8), vagrant's bsdtar has the error I posted.

On Thursday, May 21, 2015 at 12:32:35 PM UTC-7, Michael Legleux wrote:

[Ethan S.]

Are you running vagrant in a command prompt with administrative privileges or using powershell?

--
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/X0Q-TCmJ59Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.

[Alvaro Miranda]

What version of Vagrant there?

vagrant version

can you update to 1.7.4?

Thanks

Alvaro

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