Dev Container

SRB provides a customizable Dev Container in devcontainer.json.

Prerequisites

For Docker, GPU, and GUI host setup, see Docker installation.

• Visual Studio Code (VS Code)
• the Dev Containers extension
• the code CLI available on your host if you want to use the helper script below

The Dev Container uses the repository Dockerfile, mounts your local checkout into /root/ws, forwards X11, and reuses host-side Omniverse / shader caches to avoid rebuilding them every time. Its target simulator pair is listed under System Requirements. A Dev Container build or import check does not replace the pair’s Docker acceptance run.

The source image contract uses /root/isaac-sim and /root/ws. Host cache roots are listed in Clean Cache, except ~/.cache/simforge; SimForge cleanup delegates to simforge clean. The container also reuses data at ~/.nvidia-omniverse/data/ov and ~/.nvidia-omniverse/data/isaac-sim, and logs at ~/.nvidia-omniverse/logs and ~/.nvidia-omniverse/logs/isaac-sim. For ownership markers and cleanup commands, see Clean Cache.

Open in VS Code

In VS Code, use the Dev Containers extension:

1. Open the repository folder in VS Code:

   code /path/to/space_robotics_bench
   

2. Run Dev Containers: Reopen in Container from the Command Palette (Ctrl+Shift+P).

VS Code builds the full SRB image if needed, then attaches to the container.

If you have the VS Code CLI installed, the repository also provides a shortcut:

./.devcontainer/open.bash

Verify Container Setup

After attaching, verify the setup:

nvidia-smi
srb --help
srb cache update
echo "$DISPLAY"

The Dev Container requests all GPUs and /dev/dri directly in its configuration.

In these Docker profiles, WITH_GPU=false disables GPU passthrough. It does not remove Kit from the image or establish GPU, renderer, or hardware readiness.

For terminal access to an existing SRB container, use .docker/join.bash.