finds.dev← search

// the find

althack/vscode_ros2_workspace

★ 990 · Python · Apache-2.0 · updated Jun 2026

A template for using VSCode as an IDE for ROS2 development.

A devcontainer template that drops you into a Docker-based ROS2 development environment inside VSCode. Targets robotics developers who want a reproducible setup without manually configuring ROS2 on their host machine. The default image is `osrf/ros:jazzy-desktop-full`, so you get the full desktop environment in the container.

The VSCode tasks and launch configs are genuinely useful — debugging ROS2 launch files with GDB configured out of the box saves real setup time. CI is wired up with ament linters (cppcheck, cpplint, uncrustify, flake8, pep257) from day one, which most ROS2 projects skip until it's painful to add. The `repos_to_submodules.py` script is a practical touch for managing multi-package workspaces without manually tracking vcstool imports. The template is ROS version-agnostic now — swapping the Dockerfile `FROM` line is all you need.

UID/GID mismatch is a manual fix and the README buries it in the FAQ — first-time Linux users will hit permission errors on bind mounts before they find it. The GUI/display setup for X11, Wayland, and WSL2 is documented but fragile; three separate FAQ sections for display issues signals the underlying problem isn't solved. There's no example ROS2 package in `src/` so the template is purely scaffolding — a new user still has to know ROS2 well enough to populate it. ARM-based hosts (Apple Silicon, Raspberry Pi) aren't mentioned, and `osrf/ros:jazzy-desktop-full` has no ARM variant in the obvious `linux/amd64` form, so it silently falls back to emulation.

View on GitHub → Homepage ↗

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →