Disclaimer: I'm also a Vagrant newbie, but I had just this issue to fiddle with the other week.
I ended up rethinking my Vagrantfile <-> repository "arthitecture". Instead of having the provisioning script (I used a plain shell script) clone the (private) repository, I moved the Vagrantfile into the private repository, making it a 1st class member of the source code! Then it's suddenly trivial - once you've cloned the repo, just "vagrant up" and all source is already there. No public/private key magic inside the provisioning script, all that is outside of the scope of the Vagrantfile. Cheers, On Tuesday, April 21, 2015 at 12:32:43 PM UTC+2, Saeed Bhuta wrote: > > Hi guys, > > I'm dabbling with Vagrant for the first time. I am working on a provision > shell script which should clone a repository from Bitbucket. However I keep > getting the following error: > > ==> default: remote: Host key verification failed. >> ==> default: abort: no suitable response from remote hg! >> The SSH command responded with a non-zero exit status. Vagrant assumes >> that this means the command failed. The output for this command should be >> in the log above. Please read the output to determine what went wrong. > > > How can I rectify this? > > > I've posted more info here > <http://stackoverflow.com/questions/29753144/how-can-i-get-a-vagrant-provision-shell-script-to-successfully-clone-a-mercurial>along > > with links to the shell script and Vagrantfile. > > > Appreciate any help, > > Saeed. > -- 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.
