Installing Ansible

Ansible is an agentless automation tool that you install on a control node. From the control node, Ansible manages machines and other devices remotely (by default, over the SSH protocol).

To install Ansible for use at the command line, simply install the Ansible package on one machine (which could easily be a laptop). You do not need to install a database or run any daemons. Ansible can manage an entire fleet of remote machines from that one control node.


Before you install Ansible, review the requirements for a control node. Before you use Ansible, review the requirements for managed nodes (those end devices you want to automate). Control nodes and managed nodes have different minimum requirements.

Control node requirements

For your control node (the machine that runs Ansible), you can use any machine with Python 3.8 or newer installed. This includes Red Hat, Debian, CentOS, macOS, any of the BSDs, and so on. Windows is not supported for the control node, read more about this in Matt Davis’s blog post.


Please note that some plugins that run on the control node have additional requirements. These requirements should be listed in the plugin documentation.

When choosing a control node, remember that any management system benefits from being run near the machines being managed. If you are using Ansible to manage machines in a cloud, consider using a machine inside that cloud as your control node. In most cases Ansible will perform better from a machine on the cloud than from a machine on the open Internet.


Ansible 2.11 will make Python 3.8 a soft dependency for the control node, but will function with the aforementioned requirements. Ansible 2.12 will require Python 3.8 or newer to function on the control node. Starting with Ansible 2.11, the project will only be packaged for Python 3.8 and newer.

Managed node requirements

Although you do not need a daemon on your managed nodes, you do need a way for Ansible to communicate with them. For most managed nodes, Ansible makes a connection over SSH and transfers modules using SFTP. If SSH works but SFTP is not available on some of your managed nodes, you can switch to SCP in ansible.cfg. For any machine or device that can run Python, you also need Python 2 (version 2.6 or later) or Python 3 (version 3.5 or later).


Please note that some modules have additional requirements that need to be satisfied on the ‘target’ machine (the managed node). These requirements should be listed in the module documentation.


  • If you have SELinux enabled on remote nodes, you will also want to install libselinux-python on them before using any copy/file/template related functions in Ansible. You can use the yum module or dnf module in Ansible to install this package on remote systems that do not have it.

  • By default, before the first Python module in a playbook runs on a host, Ansible attempts to discover a suitable Python interpreter on that host. You can override the discovery behavior by setting the ansible_python_interpreter inventory variable to a specific interpreter, and in other ways. See Interpreter Discovery for details.

  • Ansible’s raw module, and the script module, do not depend on a client side install of Python to run. Technically, you can use Ansible to install a compatible version of Python using the raw module, which then allows you to use everything else. For example, if you need to bootstrap Python 2 onto a RHEL-based system, you can install it as follows:

    $ ansible myhost --become -m raw -a "yum install -y python2"

Selecting an Ansible artifact and version to install

Starting with version 2.10, Ansible distributes two artifacts: a community package called ansible and a minimalist language and runtime called ansible-core (called ansible-base in version 2.10). Choose the Ansible artifact and version that matches your particular needs.

Installing the Ansible community package

The ansible package includes the Ansible language and runtime plus a range of community curated Collections. It recreates and expands on the functionality that was included in Ansible 2.9.

You can choose any of the following ways to install the Ansible community package:

  • Install the latest release with your OS package manager (for Red Hat Enterprise Linux (TM), CentOS, Fedora, Debian, or Ubuntu).

  • Install with pip (the Python package manager).

Installing ansible-core

Ansible also distributes a minimalist object called ansible-core (or ansible-base in version 2.10). It contains the Ansible language, runtime, and a short list of core modules and other plugins. You can build functionality on top of ansible-core by installing collections from Galaxy, Automation Hub, or any other source.

You can choose any of the following ways to install ansible-core:

  • Install ansible-core (version 2.11 and greater) or ansible-base (version 2.10) with pip.

  • Install ansible-core (version 2.11 and greater) RPM package with dnf.

  • Install ansible-core from source from the ansible/ansible GitHub repository to access the development (devel) version to develop or test the latest features.


You should only run ansible-core from devel if you are modifying ansible-core, or trying out features under development. This is a rapidly changing source of code and can become unstable at any point.

Ansible generally creates new releases twice a year. See Releases and maintenance for information on release timing and maintenance of older releases.

Installing and upgrading Ansible with pip

Ansible can be installed on many systems with pip, the Python package manager.

Prerequisites: Installing pip

If pip is not already available on your system, run the following commands to install it:

$ curl -o
$ python --user

You may need to perform some additional configuration before you are able to run Ansible. See the Python documentation on installing to the user site for more information.

Installing Ansible with pip


If you have Ansible 2.9 or older installed or Ansible 3, see Upgrading Ansible with pip.

Once pip is installed, you can install Ansible:

$ python -m pip install --user ansible

In order to use the paramiko connection plugin or modules that require paramiko, install the required module 1:

$ python -m pip install --user paramiko

If you wish to install Ansible globally, run the following commands:

$ sudo python
$ sudo python -m pip install ansible


Running pip with sudo will make global changes to the system. Since pip does not coordinate with system package managers, it could make changes to your system that leaves it in an inconsistent or non-functioning state. This is particularly true for macOS. Installing with --user is recommended unless you understand fully the implications of modifying global files on the system.


Older versions of pip default to, which no longer works. Please make sure you have the latest version of pip before installing Ansible. If you have an older version of pip installed, you can upgrade by following pip’s upgrade instructions .

Installing Ansible in a virtual environment with pip


If you have Ansible 2.9 or older installed or Ansible 3, see Upgrading Ansible with pip.

Ansible can also be installed inside a new or existing virtualenv:

$ python -m virtualenv ansible  # Create a virtualenv if one does not already exist
$ source ansible/bin/activate   # Activate the virtual environment
$ python -m pip install ansible

Upgrading Ansible with pip

Upgrading from 2.9 or earlier to 2.10

Starting in version 2.10, Ansible is made of two packages. When you upgrade from version 2.9 and older to version 2.10 or later, you need to uninstall the old Ansible version (2.9 or earlier) before upgrading. If you do not uninstall the older version of Ansible, you will see the following message, and no change will be performed:

Cannot install ansible-base with a pre-existing ansible==2.x installation.

Installing ansible-base with ansible-2.9 or older currently installed with
pip is known to cause problems. Please uninstall ansible and install the new

pip uninstall ansible
pip install ansible-base


As explained by the message, to upgrade you must first remove the version of Ansible installed and then install it to the latest version.

$ pip uninstall ansible
$ pip install ansible

Upgrading from Ansible 3 or ansible-core 2.10

ansible-base only exists for version 2.10 and in Ansible 3. In 2.11 and later, the package is called ansible-core. Before installing ansible-core or Ansible 4, you must uninstall ansible-base if you have installed Ansible 3 or ansible-base 2.10.

To upgrade to ansible-core:

pip uninstall ansible-base
pip install ansible-core

To upgrade to Ansible 4:

pip uninstall ansible-base
pip install ansible

Installing Ansible on specific operating systems

Follow these instructions to install the Ansible community package on a variety of operating systems.

Installing Ansible on RHEL, CentOS, or Fedora

On Fedora:

$ sudo dnf install ansible


$ sudo yum install ansible

On CentOS:

$ sudo yum install epel-release
$ sudo yum install ansible

RPMs for currently supported versions of RHEL and CentOS are also available from EPEL.

Ansible can manage older operating systems that contain Python 2.6 or higher.

Installing Ansible on Ubuntu

Ubuntu builds are available in a PPA here.

To configure the PPA on your machine and install Ansible run these commands:

$ sudo apt update
$ sudo apt install software-properties-common
$ sudo add-apt-repository --yes --update ppa:ansible/ansible
$ sudo apt install ansible


On older Ubuntu distributions, “software-properties-common” is called “python-software-properties”. You may want to use apt-get instead of apt in older versions. Also, be aware that only newer distributions (in other words, 18.04, 18.10, and so on) have a -u or --update flag, so adjust your script accordingly.

Debian/Ubuntu packages can also be built from the source checkout, run:

$ make deb

Installing Ansible on Debian

Debian users may use the same source as the Ubuntu PPA (using the following table).



Debian 11 (Bullseye)


Ubuntu 20.04 (Focal)

Debian 10 (Buster)


Ubuntu 18.04 (Bionic)

Debian 9 (Stretch)


Ubuntu 16.04 (Xenial)

Debian 8 (Jessie)


Ubuntu 14.04 (Trusty)


As of Ansible 4.0.0, new releases will only be generated for Ubuntu 18.04 (Bionic) or later releases.

Add the following line to /etc/apt/sources.list or /etc/apt/sources.list.d/ansible.list:


Example for Debian 11 (Bullseye)

deb focal main

Then run these commands:

$ sudo apt-key adv --keyserver --recv-keys 93C4A3FD7BB9C367
$ sudo apt update
$ sudo apt install ansible

Installing Ansible on Gentoo with portage

$ emerge -av app-admin/ansible

To install the newest version, you may need to unmask the Ansible package prior to emerging:

$ echo 'app-admin/ansible' >> /etc/portage/package.accept_keywords

Installing Ansible on FreeBSD

Though Ansible works with both Python 2 and 3 versions, FreeBSD has different packages for each Python version. So to install you can use:

$ sudo pkg install py27-ansible


$ sudo pkg install py37-ansible

You may also wish to install from ports, run:

$ sudo make -C /usr/ports/sysutils/ansible install

You can also choose a specific version, for example ansible25.

Older versions of FreeBSD worked with something like this (substitute for your choice of package manager):

$ sudo pkg install ansible

Installing Ansible on macOS

The preferred way to install Ansible on a Mac is with pip.

The instructions can be found in Installing and upgrading Ansible with pip. If you are running macOS version 10.12 or older, then you should upgrade to the latest pip to connect to the Python Package Index securely. It should be noted that pip must be run as a module on macOS, and the linked pip instructions will show you how to do that.


If you have Ansible 2.9 or older installed or Ansible 3, see Upgrading Ansible with pip.


macOS by default is configured for a small number of file handles, so if you want to use 15 or more forks you’ll need to raise the ulimit with sudo launchctl limit maxfiles unlimited. This command can also fix any “Too many open files” errors.

If you are installing on macOS Mavericks (10.9), you may encounter some noise from your compiler. A workaround is to do the following:

$ CFLAGS=-Qunused-arguments CPPFLAGS=-Qunused-arguments pip install --user ansible

Installing Ansible on Solaris

Ansible is available for Solaris as SysV package from OpenCSW.

# pkgadd -d
# /opt/csw/bin/pkgutil -i ansible

Installing Ansible on Arch Linux

Ansible is available in the Community repository:

$ pacman -S ansible

The AUR has a PKGBUILD for pulling directly from GitHub called ansible-core-git.

Also see the Ansible page on the ArchWiki.

Installing Ansible on Slackware Linux

Ansible build script is available in the repository. Can be built and installed using sbopkg.

Create queue with Ansible and all dependencies:

# sqg -p ansible

Build and install packages from a created queuefile (answer Q for question if sbopkg should use queue or package):

# sbopkg -k -i ansible

Installing Ansible on Clear Linux

Ansible and its dependencies are available as part of the sysadmin host management bundle:

$ sudo swupd bundle-add sysadmin-hostmgmt

Update of the software will be managed by the swupd tool:

$ sudo swupd update

Installing and running the devel branch from source

In Ansible 2.10 and later, the ansible/ansible repository contains the code for basic features and functions, such as copying module code to managed nodes. This code is also known as ansible-core.

New features are added to ansible-core on a branch called devel. If you are testing new features, fixing bugs, or otherwise working with the development team on changes to the core code, you can install and run devel.


You should only install and run the devel branch if you are modifying ansible-core or trying out features under development. This is a rapidly changing source of code and can become unstable at any point.


If you want to use Ansible AWX as the control node, do not install or run the devel branch of Ansible. Use an OS package manager (like apt or yum) or pip to install a stable version.

If you are running Ansible from source, you may also wish to follow the Ansible GitHub project. We track issues, document bugs, and share feature ideas in this and other related repositories.

For more information on getting involved in the Ansible project, see the Ansible Community Guide. For more information on creating Ansible modules and Collections, see the Developer Guide.

Installing devel from GitHub with pip

You can install the devel branch of ansible-core directly from GitHub with pip:

$ python -m pip install --user


If you have Ansible 2.9 or older installed or Ansible 3, see Upgrading Ansible with pip.

You can replace devel in the URL mentioned above, with any other branch or tag on GitHub to install older versions of Ansible (prior to ansible-base 2.10.), tagged alpha or beta versions, and release candidates. This installs all of Ansible.

$ python -m pip install --user

See Running the devel branch from a clone for instructions on how to run ansible-core directly from source.

Installing devel from GitHub by cloning

You can install the devel branch of ansible-core by cloning the GitHub repository:

$ git clone
$ cd ./ansible

The default branch is devel.

Running the devel branch from a clone

ansible-core is easy to run from source. You do not need root permissions to use it and there is no software to actually install. No daemons or database setup are required.

Once you have installed the ansible-core repository by cloning, setup the Ansible environment:

Using Bash:

$ source ./hacking/env-setup

Using Fish:

$ source ./hacking/

If you want to suppress spurious warnings/errors, use:

$ source ./hacking/env-setup -q

If you do not have pip installed in your version of Python, install it:

$ curl -o
$ python --user

Ansible also uses the following Python modules that need to be installed 1:

$ python -m pip install --user -r ./requirements.txt

To update the devel branch of ansible-core on your local machine, use pull-with-rebase so any local changes are replayed.

$ git pull --rebase
$ git pull --rebase #same as above
$ git submodule update --init --recursive

After you run the the env-setup script, you will be running from the source code. The default inventory file will be /etc/ansible/hosts. You can optionally specify an inventory file (see How to build your inventory) other than /etc/ansible/hosts:

$ echo "" > ~/ansible_hosts
$ export ANSIBLE_INVENTORY=~/ansible_hosts

You can read more about the inventory file at How to build your inventory.

Confirming your installation

Whatever method of installing Ansible you chose, you can test that it is installed correctly with a ping command:

$ ansible all -m ping --ask-pass

You can also use “sudo make install”.

Finding tarballs of tagged releases

If you are packaging Ansible or wanting to build a local package yourself, and you want to avoid a git checkout, you can use a tarball of a tagged release. You can download the latest stable release from PyPI’s ansible package page. If you need a specific older version, beta version, or release candidate, you can use the pattern{{VERSION}}.tar.gz. VERSION must be the full version number, for example 3.1.0 or 4.0.0b2. You can make VERSION a variable in your package managing system that you update in one place whenever you package a new version.


If you are creating your own Ansible package, you must also download or package ansible-core (or ansible-base for packages based on 2.10.x) from PyPI as part of your Ansible package. You must specify a particular version. Visit the PyPI project pages to download files for ansible-core or ansible-base.

These releases are also tagged in the git repository with the release version.

Adding Ansible command shell completion

As of Ansible 2.9, you can add shell completion of the Ansible command line utilities by installing an optional dependency called argcomplete. argcomplete supports bash, and has limited support for zsh and tcsh.

You can install python-argcomplete from EPEL on Red Hat Enterprise based distributions, and or from the standard OS repositories for many other distributions.

For more information about installation and configuration, see the argcomplete documentation.

Installing argcomplete on RHEL, CentOS, or Fedora

On Fedora:

$ sudo dnf install python-argcomplete

On RHEL and CentOS:

$ sudo yum install epel-release
$ sudo yum install python-argcomplete

Installing argcomplete with apt

$ sudo apt install python3-argcomplete

Installing argcomplete with pip

$ python -m pip install argcomplete

Configuring argcomplete

There are 2 ways to configure argcomplete to allow shell completion of the Ansible command line utilities: globally or per command.

Global configuration

Global completion requires bash 4.2.

$ sudo activate-global-python-argcomplete

This will write a bash completion file to a global location. Use --dest to change the location.

Per command configuration

If you do not have bash 4.2, you must register each script independently.

$ eval $(register-python-argcomplete ansible)
$ eval $(register-python-argcomplete ansible-config)
$ eval $(register-python-argcomplete ansible-console)
$ eval $(register-python-argcomplete ansible-doc)
$ eval $(register-python-argcomplete ansible-galaxy)
$ eval $(register-python-argcomplete ansible-inventory)
$ eval $(register-python-argcomplete ansible-playbook)
$ eval $(register-python-argcomplete ansible-pull)
$ eval $(register-python-argcomplete ansible-vault)

You should place the above commands into your shells profile file such as ~/.profile or ~/.bash_profile.

Using argcomplete with zsh or tcsh

See the argcomplete documentation.

See also

Introduction to ad hoc commands

Examples of basic commands

Working with playbooks

Learning ansible’s configuration management language

How do I handle the package dependencies required by Ansible package dependencies during Ansible installation ?

Ansible Installation related to FAQs

Mailing List

Questions? Help? Ideas? Stop by the list on Google Groups

Real-time chat

How to join Ansible chat channels


paramiko was included in Ansible’s requirements.txt prior to 2.8.