Sorry I'm not following your instructions exactly.

I just want the box that I have now to work with the default insecure 
private key like the original box did. 

Then I want to package that box and share it with other team members and I 
want them to do vagrant up and start using it immediately. 

What is the easiest way to achieve this? Honestly I thought this was a core 
use-case for Vagrant.

Also see this issue <https://github.com/mitchellh/vagrant/issues/5059>, 
there is obviously a ton of confusion about this still.



On Wednesday, March 4, 2015 at 7:28:12 PM UTC-8, Alvaro Miranda Aguilera 
wrote:
>
> On Thu, Mar 5, 2015 at 3:55 PM, David <[email protected] <javascript:>> 
> wrote: 
> > e package command. 
>
> Hello, 
>
> This is my point of view here. 
>
> The source box use the insecure key 
> by default the actual version of vagrant will remove it, to make it secure 
> the new box, use a generated pair key.. that is not being used anymore 
> vagrant can't connect to the new box. 
>
> You have 3 options here. 
>
> A. Tell vagrant in the middle box to NOT create a new safe/secure pair. 
> B. Run an Script before packaging to delete 70-persistent-net.rules 
> and put back the insecure pair key 
> C. Copy the new now secure pair to /vagrant and include it in the 
> package box plus Vagrantifle conf to use it 
>
> I will say, if this is for prototyping, just use A, just remember 
> delete 70-persistent-net.rules 
>
> On the first box, add: 
> config.ssh.insert_key = false 
>
> Alvaro. 
>

-- 
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.

Reply via email to