# ansible-runner use of /etc/ansible **URL:** \ **Category:** Ansible Project\ **Created:** [November 12, 2020, 1:37pm UTC](https://forum.ansible.com/t/ansible-runner-use-of-etc-ansible/34186 "2020-11-12T13:37:37Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Gerard\_Weatherby](https://avatars.discourse-cdn.com/v4/letter/g/f17d59/32.png) [@Gerard\_Weatherby](https://forum.ansible.com/u/Gerard_Weatherby)\ **Post date:** [November 12, 2020, 1:37pm UTC](https://forum.ansible.com/t/ansible-runner-use-of-etc-ansible/34186/1 "2020-11-12T13:37:37Z")
If I’m understanding the ansible-runner documentation correctly, it does not use /etc/ansible but requires a directory structure set up in a particular way. If that is correct, is there a tool that converts /etc/ansible into the required directory structure? ---
**Author:** ![racke](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/racke/32/4767_2.png) [@racke](https://forum.ansible.com/u/racke)\ **Post date:** [November 12, 2020, 1:56pm UTC](https://forum.ansible.com/t/ansible-runner-use-of-etc-ansible/34186/2 "2020-11-12T13:56:45Z")
> If I’m understanding the ansible-runner documentation correctly, it does not use /etc/ansible but requires a directory > structure set up in a particular way. > > If that is correct, is there a tool that converts /etc/ansible into the required directory structure? I never use /etc/ansible, but an inventory local to my playbook and a custom ansible.cfg. Regards          Racke ---
**Author:** ![Lars\_Liedtke](https://avatars.discourse-cdn.com/v4/letter/l/c68b51/32.png) [@Lars\_Liedtke](https://forum.ansible.com/u/Lars_Liedtke)\ **Post date:** [November 13, 2020, 8:28am UTC](https://forum.ansible.com/t/ansible-runner-use-of-etc-ansible/34186/3 "2020-11-13T08:28:05Z")
Same here ---
**Author:** ![vbotka](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/vbotka/32/359_2.png) [@vbotka](https://forum.ansible.com/u/vbotka)\ **Post date:** [November 13, 2020, 9:57am UTC](https://forum.ansible.com/t/ansible-runner-use-of-etc-ansible/34186/4 "2020-11-13T09:57:15Z")
Not exactly. ansible-runner is a wrapper of \*ansible\* and \*ansible-playbook\* [https://github.com/ansible/ansible-runner/blob/devel/ansible\_runner/runner\_config.py#L61](https://github.com/ansible/ansible-runner/blob/devel/ansible_runner/runner_config.py#L61) [https://github.com/ansible/ansible-runner/blob/devel/ansible\_runner/runner\_config.py#L170](https://github.com/ansible/ansible-runner/blob/devel/ansible_runner/runner_config.py#L170)         """         Performs basic checks and then properly invokes         - prepare\_inventory         - prepare\_env         - prepare\_command         It's also responsible for wrapping the command with the         proper ssh agent invocation and setting early ANSIBLE\_         environment variables. """ This means, /etc/ansible is used by \*ansible\* and \*ansible-playbook\* in the context of additional configuration by ansible-wrapper. For example, ANSIBLE\_STDOUT\_CALLBACK is limited to \*minimal\* and \*awx\_display\* only. [https://github.com/ansible/ansible-runner/blob/devel/ansible\_runner/runner\_config.py#L227](https://github.com/ansible/ansible-runner/blob/devel/ansible_runner/runner_config.py#L227)         if 'AD\_HOC\_COMMAND\_ID' in self.env:             self.env['ANSIBLE\_STDOUT\_CALLBACK'] = 'minimal'         else:             self.env['ANSIBLE\_STDOUT\_CALLBACK'] = 'awx\_display' IMHO, the source runner\_config.py is the only relevant reference to resolve issues.