25.0.17

Summary

• Build and publish the Dockerfile runtime stage as a separate multi-arch image tagged humble-<version>-runtime
• Follows the exact same build, digest export, artifact upload, and merge manifest conventions as the existing desktop and development variants

Motivation

Closes #1826

The runtime stage provides a minimal headless image based on ros:humble-ros-base without the ros-desktop and rviz2 packages included in the desktop stage. This is useful for running the scenario simulator on storage-constrained hardware (e.g. automotive SOC boards) where visualization is either handled on a separate host or not needed, roughly halving the image size compared to the desktop stage.

Changes

Single file: .github/workflows/Docker.yaml

1. Build job — added a "Build runtime stage" step targeting runtime, with digest export and artifact upload matching the existing pattern
2. Merge job — added a runtime matrix entry with image_suffix: -runtime to produce multi-arch manifests

No Dockerfile changes required — the runtime stage already exists.

Published tags after this change

Tag	Stage	Contents
humble-<version>	desktop	runtime + ros-desktop + rviz2
humble-<version>-devel	development	full build workspace with build tools
humble-<version>-runtime	runtime	minimal ros-base + compiled artifacts (new)

Test plan

• Verify the Docker workflow YAML passes CI lint/syntax checks
• Trigger a workflow_dispatch run and confirm all three variants (desktop, development, runtime) build and publish successfully for both amd64 and arm64
• Pull the published humble-<version>-runtime image and verify it runs headless simulation without desktop dependencies

Related Issues