Hello Francisco, Vagrant guest is created in a two step task
first step, download the base box, second step, create the guest from the base box. if you do this manually, the commands are like this: vagrant box add user/box vagrant up the first step will download the box, and put it on the HOME/.vagrant.d/boxes/<somwhere> and the second will use this base box to create the end guest. Vagrant is also smart, if the first time you do a vagrant box, it will download the box, and save it on the boxes folder, and then create the guest from the template this is why, after a vagrant destroy just the guest, and not the base box is deleted. vagrant box list vagrant box -h are the commands that apply on boxes, so there is how to delete old boxes when you want to do it. hope this clarify the part of boxes/destroy Alvaro On Wed, Apr 8, 2015 at 7:56 AM, Francisco Quintero <[email protected]> wrote: > I had this issue before with every box I use. Solved it issuing vagrant > destroy and then vagrant up. > > Vagrant detroy cleans all proceses related to the virtual machine. At first > I thought it would delete my vm.box image but it didn't. > > On Friday, February 6, 2015 at 7:33:56 PM UTC-5, [email protected] wrote: >> >> This is my first Vagrant box. I have Vagrant 1.7.2 and Virtualbox 4.3.20 >> on a Windows 7 host. >> >> I used a bitnami box to build my vm without x windows. I followed >> instructions from this link - >> https://github.com/hollodotme/Helpers/blob/master/Tutorials/vagrant/self-hosted-vagrant-boxes-with-versioning.md >> - to prepare for creating the vagrant box. >> >> I did a vagrant up and I keep getting 'Remote connection disconnect.' I >> hit ctrl+c and did a 'vagrant halt'. I booted up the new vm from virtualbox >> directly. It gets me to the login prompt. I tried 'vagrant ssh' and I get >> this error: 'ssh_exchange_identification: read: The connection was aborted'. >> >> I did a 'vagrant destroy and started over. I edited the Vagrantfile to >> allow GUI to be visible. I am able to get to get to the login prompt in the >> VBox UI and I still get the 'Remote connection disconnect' on the console. >> >> After this, I upgraded to Vagrant 1.7.2 and the issue is still there. >> >> I found other forum posts in this group about the same error message, but >> none of them seem to have the exact same problem. >> >> $ vagrant up >> Bringing machine 'default' up with 'virtualbox' provider... >> ==> default: Importing base box 'dashing_bitnami'... >> ==> default: Matching MAC address for NAT networking... >> ==> default: Setting the name of the VM: >> VagrantTest_default_1423268267150_49487 >> >> ==> default: Clearing any previously set network interfaces... >> ==> default: Preparing network interfaces based on configuration... >> default: Adapter 1: nat >> ==> default: Forwarding ports... >> default: 22 => 2222 (adapter 1) >> ==> default: Booting VM... >> ==> default: Waiting for machine to boot. This may take a few minutes... >> default: SSH address: 127.0.0.1:2222 >> default: SSH username: vagrant >> default: SSH auth method: private key >> default: Warning: Connection timeout. Retrying... >> default: Warning: Remote connection disconnect. Retrying... >> default: Warning: Remote connection disconnect. Retrying... >> default: Warning: Remote connection disconnect. Retrying... >> default: Warning: Remote connection disconnect. Retrying... >> default: Warning: Remote connection disconnect. Retrying... >> default: Warning: Remote connection disconnect. Retrying... >> > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
