Installation Guide

Welcome to the Ansible Installation Guide!

Basics / What Will Be Installed

Ansible by default manages machines over the SSH protocol.

Once Ansible is installed, it will not add a database, and there will be no daemons to start or keep running. You only need to install it on one machine (which could easily be a laptop) and it can manage an entire fleet of remote machines from that central point. When Ansible manages remote machines, it does not leave software installed or running on them, so there’s no real question about how to upgrade Ansible when moving to a new version.

What Version To Pick?

Because it runs so easily from source and does not require any installation of software on remote machines, many users will actually track the development version.

Ansible’s release cycles are usually about four months long. Due to this short release cycle, minor bugs will generally be fixed in the next release versus maintaining backports on the stable branch. Major bugs will still have maintenance releases when needed, though these are infrequent.

If you are wishing to run the latest released version of Ansible and you are running Red Hat Enterprise Linux (TM), CentOS, Fedora, Debian, or Ubuntu, we recommend using the OS package manager.

For other installation options, we recommend installing via “pip”, which is the Python package manager, though other options are also available.

If you wish to track the development release to use and test the latest features, we will share information about running from source. It’s not necessary to install the program to run from source.

Control Machine Requirements

Currently Ansible can be run from any machine with Python 2 (version 2.7) or Python 3 (versions 3.5 and higher) installed. Windows isn’t supported for the control machine.

This includes Red Hat, Debian, CentOS, macOS, any of the BSDs, and so on.


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” error.


Please note that some modules and plugins have additional requirements. For modules these need to be satisfied on the ‘target’ machine and should be listed in the module specific docs.

Managed Node Requirements

On the managed nodes, you need a way to communicate, which is normally ssh. By default this uses sftp. If that’s not available, you can switch to scp in ansible.cfg. You also need Python 2 (version 2.6 or later) or Python 3 (version 3.5 or later).


  • 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, Ansible uses the python interpreter located at /usr/bin/python to run its modules. However, some Linux distributions may only have a Python 3 interpreter installed to /usr/bin/python3 by default. On those systems, you may see an error like:

    "module_stdout": "/bin/sh: /usr/bin/python: No such file or directory\r\n"

    you can either set the ansible_python_interpreter inventory variable (see Working with Inventory) to point at your interpreter or you can install a Python 2 interpreter for modules to use. You will still need to set ansible_python_interpreter if the Python 2 interpreter is not installed to /usr/bin/python.

  • Ansible’s “raw” module (for executing commands in a quick and dirty way) and the script module don’t even need Python installed. So 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 via

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

Installing the Control Machine

Latest Release via DNF or Yum

On Fedora:

$ sudo dnf install ansible

On RHEL and CentOS:

$ sudo yum install ansible

RPMs for RHEL 7 are available from the Ansible Engine repository.

To enable the Ansible Engine repository, run the following command:

$ sudo subscription-manager repos --enable rhel-7-server-ansible-2.6-rpms

RPMs for currently supported versions of RHEL, CentOS, and Fedora are available from EPEL as well as

Ansible version 2.4 and later can manage earlier operating systems that contain Python 2.6 or higher.

You can also build an RPM yourself. From the root of a checkout or tarball, use the make rpm command to build an RPM you can distribute and install.

$ git clone
$ cd ./ansible
$ make rpm
$ sudo rpm -Uvh ./rpm-build/ansible-*.noarch.rpm

Latest Releases via Apt (Ubuntu)

Ubuntu builds are available in a PPA here.

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

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


On older Ubuntu distributions, “software-properties-common” is called “python-software-properties”.

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

$ make deb

You may also wish to run from source to get the latest, which is covered below.

Latest Releases via Apt (Debian)

Debian users may leverage the same source as the Ubuntu PPA.

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

deb trusty main

Then run these commands:

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


This method has been verified with the Trusty sources in Debian Jessie and Stretch but may not be supported in earlier versions.

Latest Releases via Portage (Gentoo)

$ 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


The current default Python slot on Gentoo is version 3.4. Ansible needs Python-3.5 or higher so you will need to :ref:`bootstrap <managed_node_requirements> a compatible version onto the machines.

Latest Releases via pkg (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 py36-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, i.e ansible25.

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

$ sudo pkg install ansible

Latest Releases on macOS

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

The instructions can be found in Latest Releases via Pip section. If you are running macOS version 10.12 or older, then you ought to upgrade to the latest pip (9.0.3 or newer) to connect to the Python Package Index securely.

Latest Releases via OpenCSW (Solaris)

Ansible is available for Solaris as SysV package from OpenCSW.

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

Latest Releases via Pacman (Arch Linux)

Ansible is available in the Community repository:

$ pacman -S ansible

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

Also see the Ansible page on the ArchWiki.

Latest Releases via Pip

Ansible can be installed via “pip”, the Python package manager. If ‘pip’ isn’t already available in your version of Python, you can get pip by:

$ sudo easy_install pip

Then install Ansible with [1]:

$ sudo pip install ansible

Or if you are looking for the latest development version:

$ pip install git+[email protected]

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

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

Readers that use virtualenv can also install Ansible under virtualenv, though we’d recommend to not worry about it and just install Ansible globally. Do not use easy_install to install Ansible directly.


Older versions of pip defaults to, which no longer works. Please make sure you have an updated pip (version 10 or greater) installed before installing Ansible. Refer here about installing latest pip.

Tarballs of Tagged Releases

Packaging Ansible or wanting to build a local package yourself, but don’t want to do a git checkout? Tarballs of releases are available on the Ansible downloads page.

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

Running From Source

Ansible is easy to run from a checkout - root permissions are not required to use it and there is no software to actually install. No daemons or database setup are required. Because of this, many users in our community use the development version of Ansible all of the time so they can take advantage of new features when they are implemented and easily contribute to the project. Because there is nothing to install, following the development version is significantly easier than most open source projects.


If you are intending to use Tower as the Control Machine, do not use a source install. Please use OS package manager (like apt/yum) or pip to install a stable version.

To install from source, clone the Ansible git repository:

$ git clone --recursive
$ cd ./ansible

Once git has cloned the Ansible repository, 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 don’t have pip installed in your version of Python, install pip:

$ sudo easy_install pip

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

$ sudo pip install -r ./requirements.txt

To update ansible checkouts, use pull-with-rebase so any local changes are replayed.

$ git pull --rebase

Note: when updating Ansible checkouts that are v2.2 and older, be sure to not only update the source tree, but also the “submodules” in git which point at Ansible’s own modules.

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

Once running the env-setup script you’ll be running from checkout and the default inventory file will be /etc/ansible/hosts. You can optionally specify an inventory file (see Working with Inventory) other than /etc/ansible/hosts:

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


ANSIBLE_INVENTORY is available starting at 1.9 and substitutes the deprecated ANSIBLE_HOSTS

You can read more about the inventory file in later parts of the manual.

Now let’s test things with a ping command:

$ ansible all -m ping --ask-pass

You can also use “sudo make install”.

Ansible on GitHub

You may also wish to follow the GitHub project if you have a GitHub account. This is also where we keep the issue tracker for sharing bugs and feature ideas.

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
#ansible IRC chat channel
[1](1, 2) If you have issues with the “pycrypto” package install on macOS, then you may need to try CC=clang sudo -E pip install pycrypto.