-
Bug
-
Resolution: Done
-
Minor
-
DO374 - RHAAP2.2-en-2-20240606
-
None
-
False
-
-
False
-
1
-
-
-
en-US (English)
URL: | ch01s03 |
Reporter RHNID: | dhashimo |
Section title: | Running Playbooks with Automation Content Navigator |
Language: | English |
Issue description
I believe this statement is incorrect:
"The main difference between authenticating ansible-navigator and ansible-playbook to managed hosts is that ansible-navigator runs the playbook inside a container that cannot access your ~/.ssh directory"
The ~/.ssh directory is mounted on the container, and its config file is actually used for the connection:
[cloud-user@dh-191 ans]$ ansible-navigator --pp missing exec findmnt | grep ssh
-/root/.ssh /dev/vda4[/home/cloud-user/.ssh] xfs rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota |
-/home/runner/.ssh /dev/vda4[/home/cloud-user/.ssh] xfs rw,relatime,seclabel,attr2,inode64,logbufs=8,logbsize=32k,noquota |
ssh-agent is used if available, but the statement that the ~/.ssh is not accessible from the execution environment is incorrect.
https://github.com/ansible/ansible-navigator/blob/v2.1.0/docs/faq.md#ssh-keys