vagrant package: rootfs duplicate files

[gwillem]

So I want to repackage a box to speed up the time taken by the CM.

vagrant package $VM --output vm.box.tgz
cd ~/.vagrant.d/boxes/precise64
mv lxc lxc-backup
mkdir lxc
cd lxc
tar xfvz ~/vm.box.tgz
vagrant up 

but this yields (VAGRANT_LOG=DEBUG):

DEBUG subprocess: stdout: Extracting /home/willem/.vagrant.d/boxes/precise64/lxc/rootfs.tar.gz ...
DEBUG subprocess: stderr: tar: resolvconf: Cannot open: File exists
DEBUG subprocess: stderr: tar: init: Cannot open: File exists
DEBUG subprocess: stderr: tar: plymouth: Cannot open: File exists
DEBUG subprocess: stderr: tar: Exiting with failure status due to previous errors
DEBUG subprocess: stderr: lxc-create: container creation template for hypernode-deploy_precise04-1383060216 failed

I'm not sure why these files already exist. @fgrehm, would you have any idea how I can find the relevant tar cmd (with full paths) and examine the situation in a sandbox ?

[fgrehm]

You need to check the extract_rootfs on your ~/.vagrant.d/boxes/precise64/lxc/lxc-template. I've recently changed the code related to that so it might be the issue if you are using the new base boxes =/

[gwillem]

Aha! Yes, if I use strip-components=1, it works! So I guess the lxc-specific code for "vagrant package" needs to tar a rootfs without the leading dir name (or it needs to adjust lxc-template upon packaging).

Thanks for the quick reply!

[fgrehm]

Oh, it works with strip-components=1 or 2?
On a side note, I completely forgot to test repackaging base boxes prior to releasing them, so I can't guarantee it will work fine =/

[fgrehm]

*repackaging the new base boxes

[gwillem]

So with the new relative path, the directory layout is the same for new (vagrant package) boxes as for the existing ones, so strip-components=2 will work in all cases.

[fgrehm]

Awesome! Thanks for helping out, I'll close this in favor of GH-174 :)