exec-local-docker

Executes TensorRT-LLM workloads in local Docker containers with background monitoring and log-based result reporting.

14.5k|2.7k|Updated Aug 16, 2023
One-click install
npx skills add https://github.com/NVIDIA/TensorRT-LLM --skill exec-local-docker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exec-local-docker
Source: https://github.com/NVIDIA/TensorRT-LLM/tree/main/.claude/skills/exec-local-docker
Command: npx skills add https://github.com/NVIDIA/TensorRT-LLM --skill exec-local-docker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running TensorRT-LLM tests, evaluations, and benchmarks inside Docker requires manually launching containers, watching for hangs, and parsing logs to determine pass/fail status. This Skill automates that entire loop so an orchestrator can fire off a workload and receive a structured result without babysitting the process.

Core Features & Use Cases

  • Background Docker Execution: Launches a fully-resolved docker run command in the background with output tee'd to a log file, never blocking the foreground.
  • Hang Detection and Recovery: Runs a monitoring loop that greps the log for hang indicators and kills the container automatically, reporting a HANG_DETECTED status.
  • Image Resolution and Build: Optionally detects GPU type and host CPU architecture, resolves the correct container image tag, and compiles the project before launching.
  • Workflow-Aware Result Parsing: Parses logs differently for pytest, eval, custom, and benchmark workloads, returning a structured status report with exit code, summary, and errors.
  • Use Case: An orchestrator needs to run a pytest suite for a TensorRT-LLM model on an H100 machine. It passes the Docker command, log path, and success patterns; the Skill builds the image, runs the tests, watches for hangs, and reports PASSED with the pytest summary line.

Quick Start

Run this TensorRT-LLM pytest workload in local Docker using the provided docker command, monitor the log for hangs, and report whether the tests passed or failed.

Frequently Asked Questions about exec-local-docker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run TensorRT-LLM tests in a local Docker container?

Pass a complete docker run command, a log file path, and success/failure patterns to the executor. It launches the command in the background, tees output to the log, monitors for hangs, and returns a structured status report with the exit code and parsed summary.

How do I detect and kill a hung Docker container running GPU workloads?

Run a background monitoring loop that greps the workload log every 60 seconds for hang indicators like 'hang detected'. When found, kill the container with docker kill filtered by image ancestor and report a HANG_DETECTED status instead of waiting indefinitely.

Does the executor support different GPU types like H100 and B200?

Yes, it detects the GPU via nvidia-smi or a job spec field and maps it to a build architecture flag. H100 and H200 map to 90-real, B200/GB200/B300/GB300 to 100-real, A100 to 80-real, and L40S to 89-real, defaulting to 100-real when unknown.

Why did my Docker workload fail immediately after launch?

An exit code within seconds usually means the container image does not exist locally or the command is malformed. Check that the image tag is present with docker images, and read the first 50 lines of the log file to catch import failures or setup crashes.

What log patterns indicate success for pytest and eval workloads?

For pytest, look for the 'X passed, Y failed in Zs' summary line. For eval workloads, look for 'accuracy:' or 'score:' lines and watch for assertion messages like 'Expected accuracy >= X, but got Y' indicating failure.