Reused that box description for proof-of-concept jenkins-in-a-box for M$-bound developers.
The ssh-call to ssh into the once enrolled box was (information per vagrant ssh-config
):
$ ssh [email protected] -p 2200 -i /d/tools/vagrant-aweijnitz/.vagrant/machines/default/virtualbox/private_key -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o PasswordAuthentication=no -o IdentitiesOnly=yes -o LogLevel=FATAL
Have to look more deeply on the set of commands vagrant understands, not to forget one of them vagrant reload
on changes in the configuration.
On some occasions ssh-add ~/.vagrant.d/insecure_private_key
can be useful.