I think it is working now. I did: 1.) Added back the public insecure key to ~vagrant/.ssh/authorized_keys 2.) added config.ssh.insert_key = false to my Vagrantfile
I think this corresponds to your Option A? However I don't have a file 70-persistent-net.rules on my system...maybe because I am using CentOs rather than Ubuntu. I don't really understand Option B. Are you suggesting that I use a new secure keypair during my development and then when I package the box for someone else that I add back the insecure key? I guess that makes sense, but how do you mean run a script -- just manually run it or is there a hook or something? Thanks 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.
