Normally, you can ssh into a Vagrant-managed VM with vagrant ssh
. There are two options:
insecure_private_key
generated by
I think that you should try using the inventory generated by vagrant. This will save you from having to maintain an Ansible inventory in addition to your Vagrantfile.
For example, you should find an inventory like this used for vagrant ssh
:
cat .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory
>>>
# Generated by Vagrant
default ansible_host=127.0.0.1 ansible_port=2222 ansible_user='vagrant' ansible_ssh_private_key_file='/home/someone/coding-in-a-project/.vagrant/machines/default/virtualbox/private_key'
You will be able to run ansible
ad-hoc commands and ansible-playbook
commands.
(specify this maybe for your needs : --private-key=~/.ssh/your_private_key
)
ansible default -i .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory -m ansible.builtin.shell -a 'echo foobar'
ansible-playbook -i .vagrant/provisioners/ansible/inventory/vagrant_ansible_inventory playbook.yml
source : https://docs.ansible.com/ansible/latest/scenario_guides/guide_vagrant.html
The problem probably lies within your hosts/inventory
file. You need to add the proper connection configuration for Ansible therein, save and re-run.
192.168.50.5 ansible_ssh_port=22 ansible_ssh_user=vagrant ansible_ssh_private_key_file=~/.ssh/id_rsa
If you are not using port 22
, adjust the ansible_ssh_port
in your hosts file accordingly.
It is also a possibility that you have not setup your pubkey in Vagrant, hence this would also not work. To test this, run:
vagrant ssh-config | grep IdentityFile
# result should be your private key and not
# .vagrant/machines/default/virtualbox/private_key
If you have not put your pubkey
in the Vagrant vm, you will need to add that before you can try your private key.
Reference: http://docs.ansible.com/ansible/intro_inventory.html#list-of-behavioral-inventory-parameters
Reference: https://docs.vagrantup.com/v2/cli/ssh_config.html