IsaacLab (Docker mount)

Languages: English | 中文

This repository is intended to be used together with FLUX. Both are bind-mounted into the same container image so you can work on the host checkouts from /workspace inside the container.

Pull the image

docker pull quay.io/zeyinggong/flux:v0

Image: quay.io/zeyinggong/flux:v0

Clone this repository

git clone https://github.com/Zeying-Gong/IsaacLab.git

(Also clone the FLUX repository.)

Run the container

Replace the host paths below with your local clones of FLUX and this IsaacLab repo (they map to /workspace/FLUX and /workspace/IsaacLab in the container).

docker run --name flux_v0 \
    -e "ACCEPT_EULA=Y" \
    -e "PRIVACY_CONSENT=Y" \
    -e "DISPLAY=${DISPLAY}" \
    --entrypoint bash \
    --gpus all \
    --network=host \
    --privileged \
    -v /tmp/.X11-unix:/tmp/.X11-unix \
    -v /path/to/FLUX:/workspace/FLUX \
    -v /path/to/IsaacLab:/workspace/IsaacLab \
    -w /workspace \
    -it quay.io/zeyinggong/flux:v0

• /path/to/FLUX — your local folder for Zeying-Gong/FLUX.
• /path/to/IsaacLab — your local folder for this repository.

Differences from upstream Isaac Lab

This fork is not a drop-in replacement for NVIDIA Isaac Lab. We changed the codebase for our FLUX / dynamic-scene workflow. The main behavioral differences live in:

Area	File
Dynamic scene (integrates crowd / people simulation into the scene lifecycle)	source/isaaclab/isaaclab/scene/dynamic_scene.py
Pedestrians: episode-JSON-driven people simulation (Isaac Sim replicator agents)	source/isaaclab/isaaclab/scene/people_simulation.py

Expect other files to differ as well; treat this repo as a customized Isaac Lab tree aligned with the flux:v0 image and FLUX documentation.

What else you may need

• Host setup: Docker with NVIDIA Container Toolkit so --gpus all works; an X11 display if you rely on DISPLAY and /tmp/.X11-unix (typical for GUI / Isaac Sim).
• FLUX side: Follow the FLUX repo for dataset layout, episode JSON format, and how paths under /workspace/FLUX are expected to look inside the container.
• Security: The example uses --network=host and --privileged for convenience with simulation and display; tighten these for your own threat model if you do not need them.
• Upstream docs: For generic Isaac Lab concepts not covered here, the official Isaac Lab documentation may still be useful, but APIs and behavior may not match this fork exactly.