https://jhooq.com/tags/ansible-installation/Recent content in Ansible Installation on JhooqHugo -- gohugo.ioenJhooqWed, 06 Jul 2022 00:00:00 +0000https://jhooq.com/ansible-installation/Wed, 06 Jul 2022 00:00:00 +0000https://jhooq.com/ansible-installation/ <h2 id="tldr">TL;DR</h2> <ul> <li><strong>Ansible only needs to be installed on the control node</strong>, the machine you run <code>ansible</code> from. Managed nodes need Python and SSH, not Ansible (<a href="https://raw.githubusercontent.com/ansible/ansible-documentation/devel/docs/docsite/rst/installation_guide/intro_installation.rst">installation guide</a>).</li> <li><strong>Fastest route on Linux and macOS:</strong> <code>python3 -m venv ansible-env</code>, <code>ansible-env/bin/pip install ansible</code>, then <code>ansible --version</code>. On 2026-11-03 this gave me Ansible 12.3.0 with ansible-core 2.19.15 and a working <code>ansible localhost -m ping</code>.</li> <li><strong>The trap:</strong> pip picks the newest release your Python supports. ansible-core 2.20 and 2.21 need Python 3.12 or newer, 2.22 needs 3.13 or newer, so on Python 3.11 you silently stay on 2.19.</li> <li><strong>Windows:</strong> there is no native control node. Install WSL and follow the Linux steps inside it (<a href="https://raw.githubusercontent.com/ansible/ansible-documentation/devel/docs/docsite/rst/os_guide/intro_windows.rst">Windows guide</a>).</li> <li><strong>Not your exact case?</strong> If you already have Ansible and need to target one machine, read <a href="https://jhooq.com/ansible-limit-hosts/">ansible --limit and hosts</a>; if you want a safe lab first, read <a href="https://jhooq.com/ansible-lab-on-laptop-with-docker/">Ansible lab on a laptop with Docker</a>.</li> </ul> <div class="video"> <iframe src="https://www.youtube.com/embed/5bEAZ0La_Xo?controls=1&rel=0" loading="lazy"></iframe> </div> <h2 id="table-of-content">Table of Content</h2> <ol> <li><a href="#1-what-you-are-installing-and-where">What you are installing and where</a></li> <li><a href="#2-pick-the-route">Pick the route</a></li> <li><a href="#3-install-with-pip-in-a-venv-linux-and-macos">Install with pip in a venv (Linux and macOS)</a></li> <li><a href="#4-install-with-pipx">Install with pipx</a></li> <li><a href="#5-ubuntu-and-debian-packages">Ubuntu and Debian packages</a></li> <li><a href="#6-fedora-centos-stream-rocky-and-almalinux">Fedora, CentOS Stream, Rocky and AlmaLinux</a></li> <li><a href="#7-macos">macOS</a></li> <li><a href="#8-windows-with-wsl">Windows with WSL</a></li> <li><a href="#9-verify-with-ad-hoc-commands">Verify with ad-hoc commands</a></li> <li><a href="#10-what-broke-when-i-ran-this">What broke when I ran this</a></li> <li><a href="#11-next-steps">Next steps</a></li> </ol> <h2 id="1-what-you-are-installing-and-where">1. What you are installing and where</h2> <p>Ansible is agentless. You install it once on the control node, and it talks to managed nodes over SSH (or WinRM for Windows targets). The managed node needs a Python interpreter to run the modules Ansible copies over, with the exception of network modules (<a href="https://raw.githubusercontent.com/ansible/ansible-documentation/devel/docs/docsite/rst/installation_guide/intro_installation.rst">installation guide</a>).</p>