Skip to main content
Translation updated
#ros2#ubuntu#development-environment#dds

Choosing a ROS 2 distribution and development environment

Use REP-2000 and the official installation documents to match an operating system, support window and hardware architecture.

The list of supported distributions is often the first part of a ROS 2 installation guide to go out of date. Here is how to make a choice using the official support matrix and repeat the process later.

Snapshot checked on August 25, 2026. Use REP-2000 to verify the current support status.

#Distribution choices as of August 25, 2026

GoalSuggested starting pointRationale
Long-term project or productROS 2 Jazzy + Ubuntu 24.04LTS combination with Jazzy support through May 2029
Evaluate new featuresROS 2 Kilted + Ubuntu 24.04Regular release with support through November 2026
Keep an existing Ubuntu 22.04 installationROS 2 HumbleSupported through May 2027. For a new installation, weigh the cost of changing the OS.
Track upcoming featuresRollingA continuously changing development distribution makes a poor fixed product baseline.

Iron reached end of support in November 2024 and Foxy in May 2023. Existing hardware can remain in use, but continued upstream security and bug fixes should no longer be assumed.

#A selection process that can be repeated

  1. Check end-of-support dates and Tier 1 platforms in REP-2000.
  2. Match the Ubuntu release to a compatible ROS distribution.
  3. Check binary-package availability in the official installation guide.
  4. Verify that the required drivers, Nav2, MoveIt, and ros2_control have releases for that distribution.
  5. Pin the distribution name and container digest in the project and record the upgrade date.

#Installing on a new Ubuntu 24.04 machine

The official deb installation procedure can change as repository and signing-key configuration evolves. Follow the official page below for the commands.

After installation, run a basic check.

source /opt/ros/$ROS_DISTRO/setup.bash
printenv ROS_DISTRO
ros2 doctor --report
ros2 run demo_nodes_cpp talker
# In a second terminal
ros2 run demo_nodes_py listener

For workspace dependencies, start with rosdep before installing individual packages with pip install.

sudo rosdep init       # Once per machine
rosdep update
rosdep install --from-paths src --ignore-src -y
colcon build --symlink-install

Official guide: Managing Dependencies with rosdep

#Choosing a DDS implementation and RMW

Select an RMW implementation according to the project’s requirements.

  • Development on a single PC: start with the default RMW.
  • Unstable Wi-Fi and many nodes: measure discovery, QoS behavior, and packet loss on the actual network.
  • Multiple potential vendors: use standard messages and QoS profiles and run a smoke test for each RMW.
  • Real-time control: measure executor behavior, allocation, and OS scheduling alongside DDS latency.
printenv RMW_IMPLEMENTATION
ros2 doctor --report

Tier 1 RMW support can vary by distribution. Check REP-2000 and the relevant release notes.

#Python environment considerations

Official binary ROS 2 packages are built for the distribution’s system Python. Mixing Conda or another Python installation into that environment can cause conflicts with rclpy or binary extensions. For a separate environment, follow the official Python packages guide and place COLCON_IGNORE in any virtual environment inside the workspace.

#Installation record template

Checked: 2026-08-25
OS: Ubuntu 24.04.x amd64/arm64
ROS_DISTRO: jazzy
Install source: official deb repository
RMW: <implementation>
Workspace commit: <sha>
rosdep snapshot: <date>
Verification: talker/listener + project smoke test

A record like this helps distinguish outdated installation instructions from project changes when a setup fails months later.

Connect