Dev Container

VerifiedCaution

Sets up and manages the isaaclab_arena Docker container for development, testing, training, and evaluation. Covers start, attach, rebuild, and flag combinations.

Sby Skills Guide Bot
DevOpsIntermediate
7/25/2026
Claude Code
#docker#dev-environment#container-management#isaac-sim#workspace-setup

Recommended for

Automated summary

Manages IsaacLab-Arena's single Docker container, which serves as the development, testing, training, and evaluation environment, resolving the per-clone container name automatically.

Strengths

  • Shows how to resolve the container bound to the current clone using a Docker volume filter instead of hardcoding a name.
  • Documents the ./docker/run_docker.sh flag combinations, including -r/-R for image rebuilds and -d/-m/-e for custom dataset, model, and eval mounts.
  • Gives the exact docker exec invocation with su and cd into /workspaces/isaaclab_arena for running commands in an already-running container.
  • Warns to call /isaac-sim/python.sh explicitly from outside the container, where the python alias is not active.

Limitations

  • Highly specific to the IsaacLab-Arena repository and its ./docker/run_docker.sh script, so it does not transfer to other projects.
  • Does not cover troubleshooting image build failures, GPU resource handling, or permission issues beyond what is described.
  • Assumes Docker is already installed and the user has the required host permissions.
When to use it

Use it whenever you need to bootstrap, start, rebuild, or run a command inside IsaacLab-Arena's containerized development environment.

When not to use it

Avoid it for work on other projects, or when you need non-Docker installation guidance or broader infrastructure troubleshooting.

Security analysis

Caution
Quality score88/100

The skill manages a legitimate Docker-based development environment with no destructive or exfiltrating instructions. However, it relies on powerful Docker execution and host directory mounts, which warrants caution even though the stated use is legitimate and scoped to the project.

Findings
  • •Uses docker exec to run arbitrary commands inside a container, which could execute unintended commands if user input is substituted without validation.
  • •The run_docker.sh script supports mounting arbitrary host directories (-d, -m, -e), granting container access to host paths.
How this analysis is made

Examples

Fresh clone bootstrap
I just cloned IsaacLab-Arena on a new machine. Set up the dev environment and confirm the isaaclab_arena package imports.
Rebuild image without cache
Rebuild the isaaclab_arena image from scratch without cache, then attach me to this clone's container.
Run a command in the running container
Start the container with my datasets in ~/datasets and models in ~/models, then run the training script inside it.

name: dev-container description: Sets up and manages the isaaclab_arena Docker container — the single environment used for Arena's development, testing, training, and evaluation. Use when the user asks to set up the dev environment, bootstrap the project, get started on a fresh clone, start developing, build or rebuild the image, start or attach to the container, or run any command inside it. Also covers ./docker/run_docker.sh flag combinations (-r rebuild, -R rebuild without cache, -d/-m/-e custom dataset/model/eval mounts), docker exec usage, and the /isaac-sim/python.sh aliasing. allowed-tools: Bash(./docker/run_docker.sh *) Bash(docker exec *) Bash(docker images *) Bash(docker ps *)

Dev Container

Arena uses a single Docker container as the dev, test, training, and eval environment. There is no separate dev container.

Each clone of the repo on the host machine gets its own container, so separate clones can run in parallel. The image (isaaclab_arena:latest) is shared, but the container name is isaaclab_arena-latest for the folder named IsaacLab-Arena and isaaclab_arena-latest-<suffix> for folders named IsaacLab-Arena_<suffix> (run_docker.sh derives the suffix automatically).

Discover this clone's container (once per session)

Never hardcode the name. At the start of a session, resolve the container mounting this clone into ARENA_CONTAINER (empty result = none running, so start one below):

ARENA_CONTAINER=$(docker ps --filter "volume=$(git rev-parse --show-toplevel)" --format '{{.Names}}' | head -1)

Run the commands below in that same shell so $ARENA_CONTAINER stays set (or substitute the literal name).

Start or attach

./docker/run_docker.sh

Idempotent: builds the (shared) image if it does not exist, starts this clone's container if it is not running, then attaches. The container name is auto-derived from the clone directory; pass -s <suffix> to override it.

Common flag combinations

| Flag | Purpose | |---|---| | -r | Force image rebuild | | -R | Force image rebuild without cache | | -d <path> | Mount a custom dataset directory | | -m <path> | Mount a custom model directory | | -e <path> | Mount a custom eval directory |

Example with custom mounts:

./docker/run_docker.sh -d ~/datasets -m ~/models -e ~/eval

Run a command in the already-running container

docker exec "$ARENA_CONTAINER" su $(id -un) -c \
  "cd /workspaces/isaaclab_arena && <command>"

The repo root is mounted at /workspaces/isaaclab_arena inside the container.

Python invocation

Inside the container, python is aliased to /isaac-sim/python.sh. Both forms work, but prefer /isaac-sim/python.sh explicitly in docker exec invocations from outside the container, where the alias is not active.

Verify

A container is up and importable when:

docker exec "$ARENA_CONTAINER" su $(id -un) -c \
  "/isaac-sim/python.sh -c 'import isaaclab_arena; print(isaaclab_arena.__file__)'"

prints a path under /workspaces/isaaclab_arena/.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/dev-container-mrzxupk5/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/dev-container-mrzxupk5' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/dev-container-mrzxupk5/download' --output '.skill-downloads/dev-container-mrzxupk5/SKILL.md.part' && mv '.skill-downloads/dev-container-mrzxupk5/SKILL.md.part' '.skill-downloads/dev-container-mrzxupk5/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(./docker/run_docker.sh *) Bash(docker exec *) Bash(docker images *) Bash(docker ps *)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/dev-container-mrzxupk5/SKILL.md' && test -s '.skill-downloads/dev-container-mrzxupk5/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/dev-container' && cp -R '.skill-downloads/dev-container-mrzxupk5' '.claude/skills/dev-container'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/dev-container-mrzxupk5'

openskills read 'dev-container-mrzxupk5'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/dev-container-mrzxupk5/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills