I'm building a lightweight windows box for vagrant, following the guide outlined by Matt Wrock here. Matt states that as of 1.6, tarball sizes over 2GB aren't supported but I'm hoping this isn't the case with the newest version I am running. As you have guessed I'm doing this on a Windows 10 machine as my workstation. bsdtar is packaged with Vagrant and C:\HashiCorp\Vagrant\embedded\mingw\bin is in my path. I pulled another version of bsdtar off sourceforge and am having the same issue.
Output of bsdtar --version:
bsdtar 2.8.3 - libarchive 2.8.3
Using the following command: bsdtar --lzma -cvf package.box *
I see bsdtar start running in my processes, but it finishes and always produces a file that is 328kb. I'm tarballing four separate files - even when I explicitly state the files instead of using *, I get the same issue. Has anyone seen this before? I'm unable to determine what is causing this. The actual package, after compression, should be between 6-8gb in size.
EDIT: I suspect antivirus (Windows Defender) to be causing this. I have disabled and it has not resolved the issue. Issue also affects other compression types, such as GZip, though it gets farther. I suspect the process is terminating after X amount of time.
[link] [comments]