Run an Ansible Execution Environment - ansible-runner command-line tool

How to run a custom Ansible Execution Environment?

Using an Ansible Execution Environment is the latest technology to maintain up-to-date Python dependency of the Ansible collections without interfering with your Linux system. It’s the evolution of Python Virtual Environment. This initial configuration sometimes is a roadblock for some Ansible users. I’m Luca Berton and welcome to today’s episode of Ansible Pilot.

Ansible Execution Environment

• Ansible Execution Environment
• ansible-builder
• ansible-runner

Let’s talk about the Ansible Execution Environment. The Ansible Execution Environment is container images that can be utilized as Ansible control nodes. It’s the latest technology developed by Red Hat to simplify the automation process. The main advantage is a familiar environment for Development and Production images using container technology creating portable automation runtimes. This technology superseded manual Python Virtual Environments, Ansible module dependencies, and bubblewrap. Experienced users are probably familiar with many challenges managing custom Python Virtual Environments and Ansible module dependencies. Enterprise users of Ansible Automation Platform were familiar with limiting execution jobs under bubblewrap in order to isolate processes The creation is performed by the Ansible Builder tool. Ansible Builder produces a directory that acts as the build context for the container image build, containing the Containerfile, along with any other files that need to be added to the image. On the other end, the Ansible Runner tool performs the execution. The Ansible Runner enables you to run the Execution Environment as a container in the current machine. It is basically taking care that the content runs as expected.

Links

• https://www.ansible.com/products/execution-environments
• https://docs.ansible.com/automation-controller/latest/html/userguide/execution_environments.html

Playbook

How to Run an Ansible Execution Environment using ansible-runner tool. I’m going to show you how to Run the custom “my_ee” Ansible Execution Environment using the ansible-runner tool.

code

• inventory

localhost ansible_connection=local

• ping.yml

---
- name: ping module Playbook
  hosts: all
  become: false
tasks:
    - name: test connection
      ansible.builtin.ping:

execution

[devops@demo ee]$ ansible-runner run -p ping.yml --inventory inventory --container-image=my_ee .
PLAY [ping module Playbook] ********************************************************
TASK [Gathering Facts] *********************************************************
ok: [localhost]
TASK [test connection] *********************************************************
ok: [localhost]
PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   
[devops@demo ee]$

When the ansible-runner tool is not installed you should install it via the DNF command using the ansible Automation Platform subscription:

[root@demo ee]# dnf install ansible-runner

Conclusion

Now you know how to Run an Ansible Execution Environment using the ansible-runner command-line tool.

Academy

Learn the Ansible automation technology with some real-life examples in my Udemy 300+ Lessons Video Course.

My book Ansible By Examples: 200+ Automation Examples For Linux and aws System Administrator and DevOps

Donate

Want to keep this project going? Please donate

Patreon Buy me a Pizza