The ansible or ansible-core packages may be available in your operating systems package manager, and you are free to install these packages with your preferred method. Choose the package that fits your needs The following instructions use ansible, but you can substitute ansible-core if you prefer to start with a more minimal package and separately install only the Ansible Collections you require.

: Has a soft requirement of Python 3.8 as not packaged for older versions Selecting an Ansible package and version to install Īnsible’s community packages are distributed in two ways: a minimalist language and runtime package called ansible-core, and a much larger “batteries included” package called ansible, which adds a community-curated selection of Ansible Collections for automating a wide variety of devices. The table below lists the current and historical versions of Python Network modules are an exception and do not require Python on the managed device.

The managed node also needs a user account that can SSH to the node with an interactive POSIX shell. The managed node (the machine that Ansible is managing) does not require Ansible to be installed, but requires Python 2.7, or Python 3.5 - 3.11 to run Ansible library code.

Windows without WSL is not natively supported as a control node see Matt Davis’ blog post for more information. This includes Red Hat, Debian, Ubuntu, macOS, BSDs, and Windows under a Windows Subsystem for Linux (WSL) distribution. Selecting an Ansible package and version to installįor your control node (the machine that runs Ansible), you can use nearly any UNIX-like machine with Python 3.9 or newer installed.

Controlling how Ansible behaves: precedence rules.

Virtualization and Containerization Guides.

Protecting sensitive data with Ansible vault.

Installing Ansible on specific operating systems.

Adding Ansible command shell completion.

Selecting an Ansible package and version to install.

Redhat install package