vagrant box add: where does .box file get downloaded to?

Posted by Calvin Cheng on Stack Overflow See other posts from Stack Overflow or by Calvin Cheng
Published on 2012-04-14T17:25:58Z Indexed on 2012/04/14 17:28 UTC
Read the original article Hit count: 203

Filed under:

vagrant

What actually happens to the .box file (which according to the docs is simply a vbox image in tar form, in a particular format) after the first command

vagrant box add lucid32 http://files.vagrantup.com/lucid32.box

is executed?

I can't seem to find the filesystem location of lucid32.box after the download has successfully completed...

I am aware it doesn't really matter as

vagrant init lucid32
vagrant up
vagrant ssh

will get me into the vm irregardless.

But I am curious where .box is located.

Related posts about vagrant

Puppet Directory and File ownership ignored

as seen on Server Fault - Search for 'Server Fault'
Puppet seems to be lying to me, which is not very nice. I am trying to set some files and directories included in /vagrant/src to be 666 and 777, and set the ownership group to the correct Apache user (using the PuppetLabs Apache module). Output from Puppet says yes. [default] Running provisioner:… >>> More
"vagrant up" fails with "NS_ERROR_CALL_FAILED" error [on hold]

as seen on Server Fault - Search for 'Server Fault'
I am following the basic "Getting Started" guide: http://docs.vagrantup.com/v2/getting-started/index.html I ran vagrant init <etc> followed by vagrant up, but it fails with "NS_ERROR_CALL_FAILED" error. Then by enabling debug logging with VAGRANT_LOG=debug vagrant up, I get the following error… >>> More
vagrant and puppet security for ssl certificates

as seen on Server Fault - Search for 'Server Fault'
I'm pretty new to vagrant, would someone who knows more about it (and puppet) be able to explain how vagrant deals with the ssl certs needed when making vagrant testing machines that are processing the same node definition as the real production machines ? I run puppet in master / client mode, and… >>> More
Authenticate to VM using vagrant up

as seen on Super User - Search for 'Super User'
Authentication failure during Vagrant Up, while vagrant ssh and ssh vagrant@localhost -p2222 works I would like to execute a shell script using Vagrant at boot. Vagrant is unable to Authenticate, while the VM has been started using vagrant up: c:\temp\helloworld>vagrant up Bringing machine 'default'… >>> More
Vagrant ssh fails with VirtualBox

as seen on Super User - Search for 'Super User'
vagrant up fails when it gets to the ssh part: myterminal$ vagrant up [default] VM already created. Booting if its not already running... [default] Running any VM customizations... [default] Clearing any previously set forwarded ports... [default] Forwarding ports... [default] -- ssh: 22 => 2222… >>> More

Developer IT

vagrant box add: where does .box file get downloaded to? - Developer IT

vagrant box add: where does .box file get downloaded to?

vagrant

Related posts about vagrant

Puppet Directory and File ownership ignored

"vagrant up" fails with "NS_ERROR_CALL_FAILED" error [on hold]

vagrant and puppet security for ssl certificates

Authenticate to VM using vagrant up

Vagrant ssh fails with VirtualBox

Categories cloud