feat: Bump ROS 2 version from Humble to Jazzy

Author: 2b-t

templates/ReadMe.md

@@ -1,9 +1,9 @@
 # ROS and ROS 2 Docker Templates
 
-Author: [Tobit Flatscher](https://github.com/2b-t) (2021 - 2024)
+Author: [Tobit Flatscher](https://github.com/2b-t) (2021 - 2025)
 
 
 
 ## Overview
 
-This directory contains a **ROS Noetic** as well as a **ROS 2 Humble Docker workspace** template that should allow you to get started quickly with the best practices given in the documentation of this repository. The individual subdirectories contain a read-me that explains what settings can be made to the corresponding workspaces.
+This directory contains a **ROS Noetic** as well as a **ROS 2 Jazzy Docker workspace** template that should allow you to get started quickly with the best practices given in the documentation of this repository. The individual subdirectories contain a read-me that explains what settings can be made to the corresponding workspaces.

templates/ros2/ReadMe.md

@@ -1,12 +1,12 @@
-# ROS 2 Humble Docker Template
+# ROS 2 Jazzy Docker Template
 
-Author: [Tobit Flatscher](https://github.com/2b-t) (2021 - 2024)
+Author: [Tobit Flatscher](https://github.com/2b-t) (2021 - 2025)
 
 
 
 ## 0. Overview
 
-This repository contains a Docker workspace template for [**ROS 2 Humble**](https://docs.ros.org/en/humble/index.html). The idea is that a Docker is created for each project at Ament workspace level. Dependencies that are not expected to change during the course of a project are installed from Debian packages inside the Dockerfile, while proprietary dependencies that are expected to change during a project are mounted into the container and version controlled with [**`vcstool`**](https://github.com/dirk-thomas/vcstool). Only selected folders such as `dds/` and `src/` are mounted into the container so that the workspace can be compiled on the host system as well as inside the container without them interfering.
+This repository contains a Docker workspace template for [**ROS 2 Jazzy**](https://docs.ros.org/en/jazzy/index.html). The idea is that a Docker is created for each project at Ament workspace level. Dependencies that are not expected to change during the course of a project are installed from Debian packages inside the Dockerfile, while proprietary dependencies that are expected to change during a project are mounted into the container and version controlled with [**`vcstool`**](https://github.com/dirk-thomas/vcstool). Only selected folders such as `dds/` and `src/` are mounted into the container so that the workspace can be compiled on the host system as well as inside the container without them interfering.
 
 Here is an overview of the structure of this repository:
 

templates/ros2/docker/Dockerfile

@@ -1,12 +1,12 @@
 ##############
 # Base image #
 ##############
-FROM ros:humble-ros-base AS base
+FROM ros:jazzy-ros-base AS base
 
 ARG AMENT_WORKSPACE_DIR="/ament_ws"
 
 LABEL org.opencontainers.image.authors="[email protected]"
-LABEL description="ROS 2 Humble Docker template"
+LABEL description="ROS 2 Jazzy Docker template"
 LABEL version="1.0"
 
 WORKDIR ${AMENT_WORKSPACE_DIR}
@@ -57,8 +57,8 @@ RUN apt-get update \
     htop \
     iperf3 \
     iputils-ping \
-    mlocate \
     net-tools \
+    plocate \
     psmisc \
     tmux \
     xterm \
@@ -78,6 +78,10 @@ RUN apt-get update \
 RUN apt-get update \
  && apt-get install -y sudo \
  && rm -rf /var/lib/apt/lists/* \
+ # Remove user blocking UID 1000 on Ubuntu 24.04 and onwards:
+ # See https://bugs.launchpad.net/cloud-images/+bug/2005129 and
+ # https://github.com/devcontainers/images/issues/1056
+ && userdel -r ubuntu || true \
  && addgroup --gid ${GID} ${USERNAME} \
  && adduser --disabled-password --gecos '' --uid ${GID} --gid ${GID} ${USERNAME} \
  && echo ${USERNAME} ALL=\(root\) NOPASSWD:ALL > /etc/sudoers.d/${USERNAME} \