Error copying vagrant box about macinbox HOT 4 CLOSED

Hello @qrevel, and thank you for this report. I chose not to use vagrant box add because it makes the whole process take longer and use more disk space, as the box must be tar'd up and then untar'd again.

I like the suggestion to use the VAGRANT_HOME env var when available, falling back on ~/.vagrant.d/boxes as the default. I'm reluctant to create the folder if it is not found. I'd prefer to check for the existence of this folder when macinbox starts up, before any disk images are made, and to abort early with an error if it doesn't exist.

from macinbox.

Ok, currently I'm just creating the ~/.vagrant.d/boxes folder as a workaround and move the box in my VAGRANT_HOME after.

from macinbox.

I've addressed this with 97e3a0e. The VAGRANT_HOME environment variable is used if it is set, and the boxes directory is created inside of it, if necessary.

Note that you do need to make extra effort to get the environment variable across the sudo barrier, e.g.:

$ sudo "VAGRANT_HOME=${VAGRANT_HOME}" macinbox

I haven't released 3.0 yet but you can build and install the gem yourself if you follow the instructions in the README.

from macinbox.

Ok thanks I'll try it 👍

from macinbox.