I am a little stumped here and want to see if someone else can offer some insight.
I have a VM that I have provisioned using an existing vagrant base box. I loaded up some additional packages and have everything configured just right. I am now wanting to take that VM and package it again as a Vagrant box for easy distribution to the rest of my team. The VM I provisioned works great - I have pretty thoroughly tested it and am happy with the way it is setup. The problem I am encountering is that when I do a "vagrant package" on the VM and then load the newly created box with an existing Vagrantfile - the box fails upon SSH login with: web: SSH address: 127.0.0.1:2222 web: SSH username: vagrant web: SSH auth method: private key web: Warning: Connection timeout. Retrying... web: Warning: Remote connection disconnect. Retrying... web: Warning: Authentication failure. Retrying... web: Warning: Authentication failure. Retrying... I interrupt this process and then run a "vagrant ssh" and it asks me for the user password. I type in "vagrant" and I am logged into the VM. When I browse to /home/vagrant/.ssh I see that the authorized_keys file with the insecure vagrant key is missing completely. What the heck? This file definitely existed and I have verified that it still exists in the VM that I packaged the new box from. What could be causing the missing authorized_keys file in the new Vagrant box I am packaging? Thanks in advance for your help. - Aaron -- 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.
