You're reading the documentation for a development version. For the latest released version, please have a look at Galactic.

Installing ROS 2 on Ubuntu Linux

This page explains how to install ROS 2 on Ubuntu Linux from a pre-built binary package.


The pre-built binary does not include all ROS 2 packages. All packages in the ROS base variant are included, and only a subset of packages in the ROS desktop variant are included. The exact list of packages are described by the repositories listed in this ros2.repos file.

There are also Debian packages available.

System Requirements

We currently support Ubuntu Linux Focal Fossa (20.04) 64-bit x86 and 64-bit ARM. The Rolling Ridley distribution will change target platforms from time to time as new platforms are selected for development. Most people will want to use a stable ROS distribution.

Add the ROS 2 apt repository

You will need to add the ROS 2 apt repository to your system. First, make sure that the Ubuntu Universe repository is enabled by checking the output of this command.

apt-cache policy | grep universe
 500 focal/universe amd64 Packages
     release v=20.04,o=Ubuntu,a=focal,n=focal,l=Ubuntu,c=universe,b=amd64

If you don’t see an output line like the one above, then enable the Universe repository with these instructions.

sudo apt install software-properties-common
sudo add-apt-repository universe

Now add the ROS 2 apt repository to your system. First authorize our GPG key with apt.

sudo apt update && sudo apt install curl gnupg lsb-release
sudo curl -sSL  -o /usr/share/keyrings/ros-archive-keyring.gpg

Then add the repository to your sources list.

echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/ros-archive-keyring.gpg] $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/ros2.list > /dev/null

Downloading ROS 2

Binary releases of Rolling Ridley are not provided. Instead you may download nightly prerelease binaries.

  • Download the latest package for Ubuntu; let’s assume that it ends up at ~/Downloads/ros2-package-linux-x86_64.tar.bz2.

    • Note: there may be more than one binary download option which might cause the file name to differ.

  • Unpack it:

    mkdir -p ~/ros2_rolling
    cd ~/ros2_rolling
    tar xf ~/Downloads/ros2-package-linux-x86_64.tar.bz2

Installing and initializing rosdep

sudo apt update
sudo apt install -y python3-rosdep
sudo rosdep init
rosdep update

Installing the missing dependencies

Set your rosdistro according to the release you downloaded.

rosdep install --from-paths ~/ros2_rolling/ros2-linux/share --ignore-src --rosdistro rolling -y --skip-keys "console_bridge fastcdr fastrtps osrf_testing_tools_cpp poco_vendor rmw_connextdds rti-connext-dds-5.3.1 tinyxml_vendor tinyxml2_vendor urdfdom urdfdom_headers"
  1. Optional: if you want to use the ROS 1<->2 bridge, then you must also install ROS 1. Follow the normal install instructions:

Installing the python3 libraries

sudo apt install -y libpython3-dev python3-pip

Install additional DDS implementations (optional)

If you would like to use another DDS or RTPS vendor besides the default, Eclipse Cyclone DDS, you can find instructions here.

Environment setup

Sourcing the setup script

Set up your environment by sourcing the following file.

. ~/ros2_rolling/ros2-linux/setup.bash

Try some examples

In one terminal, source the setup file and then run a C++ talker:

. ~/ros2_rolling/ros2-linux/setup.bash
ros2 run demo_nodes_cpp talker

In another terminal source the setup file and then run a Python listener:

. ~/ros2_rolling/ros2-linux/setup.bash
ros2 run demo_nodes_py listener

You should see the talker saying that it’s Publishing messages and the listener saying I heard those messages. This verifies both the C++ and Python APIs are working properly. Hooray!

Next steps after installing

Continue with the tutorials and demos to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.

Using the ROS 1 bridge

The ROS 1 bridge can connect topics from ROS 1 to ROS 2 and vice-versa. See the dedicated documentation on how to build and use the ROS 1 bridge.

Additional RMW implementations (optional)

The default middleware that ROS 2 uses is Cyclone DDS, but the middleware (RMW) can be replaced at runtime. See the guide on how to work with multiple RMWs.


Troubleshooting techniques can be found here.


  1. If you installed your workspace with colcon as instructed above, “uninstalling” could be just a matter of opening a new terminal and not sourcing the workspace’s setup file. This way, your environment will behave as though there is no Rolling install on your system.

  2. If you’re also trying to free up space, you can delete the entire workspace directory with:

    rm -rf ~/ros2_rolling