Runs inside a Dev Container, SSH remote, WSL, or GitHub Codespace and
bridges Gazebo Transport's discovery/pub-sub traffic out to a native
Gazebo Sim process running on your local machine —
so a container-based ROS2 workspace can drive and observe a simulator with
native graphics performance.
Status: early / pre-alpha. The core relay mechanism is proven on a real
cross-machine deployment, but this hasn't seen broad testing yet — expect
rough edges.
Requires the companion extension
This is one half of a pair. You also need Gazebo Bridge (Host)
(RoboStar.gz-bridge-host) installed in your local VS Code — it can't be
installed automatically from inside the container, since by design it has
to run outside it. Add it to your project's devcontainer.jsoncustomizations.vscode.extensions alongside this one so the container
recommends it on open, or install it yourself in the Extensions view.
What it does
Relays local Gazebo Transport discovery/pub-sub traffic to the host side
over a control channel that forwards itself on demand — no fixed port to
declare in devcontainer.json.
Installs a gz PATH shim so a gz sim ... launch issued inside the
container is redirected to run natively on the host instead.
Exposes resource roots (a ROS_DISTRO-derived system share directory,
the open workspace folder, and any synced plugin release binaries) for
the host side to sync files from.
Commands
Gazebo Bridge: Show Remote Relay Status
Settings
gzBridge.shimPort — local-only TCP port the installed gz PATH shim
talks to (default 47101). Never forwarded outside the container; only
needs changing if you also change it in the shim's own environment.
