tao-run-on-local-docker
Local or remote Docker execution for TAO SDK job containers using a Docker daemon with NVIDIA GPU runtime. Use when running TAO jobs on the current machine, a directly attached Docker host, or a remote GPU box exposed through DOCKER_HOST. Trigger phrases include "run locally", "local Docker", "remote Docker", "use my GPU", "run on my machine", "host Docker daemon".
Security Assessment
About tao-run-on-local-docker
This NVIDIA platform skill runs TAO SDK job containers on a Docker daemon with the NVIDIA GPU runtime, either locally or on a remote GPU box exposed through DOCKER_HOST. It solves the execution-target problem for TAO workflows: a coding agent needs a consistent way to submit training, evaluation, and inference jobs as named Docker containers, whether the daemon is on the same machine or on a remote single-GPU server, with the understanding that in remote mode all filesystem paths in specs are interpreted on the remote host.
The skill emphasizes preflight verification and safe defaults. Before starting jobs it checks the host GPU runtime (NVIDIA driver branch 580, CUDA 13.0, NVIDIA Container Toolkit 1.19.0) via a setup script in check-only mode, verifies the Docker daemon is reachable, and confirms the container toolkit works by running nvidia-smi in a throwaway container. If a check fails, it prompts the user to approve and run the install command, then reruns preflight. It documents two modes: a direct-docker mode needing only Docker and the GPU runtime, and a TAO SDK wrapper mode (pip install nvidia-tao-sdk[docker]) that adds Job handles, S3 I/O wrapping, and ActionWorkflow durability, plus idempotent creation of a Docker network for job containers. It requires no platform credentials beyond Docker daemon access, and documents optional environment variables such as DOCKER_HOST, DOCKER_NETWORK, and registry credentials. A bundled benchmark reports a passing NVSkills-Eval verdict including a 100% security score.
Target users are ML engineers running TAO jobs for development, debugging, and small runs, or submitting jobs from a laptop to a remote GPU server. It is explicitly not for multi-node training, SLURM queueing, or cluster scheduling.
FAQ
What does this skill do?
It runs TAO SDK job containers as named Docker containers on a Docker daemon with the NVIDIA GPU runtime, either locally or on a remote GPU host addressed via DOCKER_HOST.
What are the prerequisites?
NVIDIA driver branch 580, CUDA Toolkit 13.0, Docker, and NVIDIA Container Toolkit 1.19.0. The TAO SDK with the docker extra is only needed for Job handles, S3 I/O wrapping, or ActionWorkflow run-folder durability.
Does it install things without asking?
GPU runtime installs are gated on user approval: preflight runs check-only and prints the install command for the user to authorize. Pip-installable Python requirements and idempotent Docker network creation are the documented exceptions it handles automatically.
When should I not use it?
It is single-node only. Do not use it for remote cluster scheduling, multi-node training, or jobs that need SLURM queueing.
What credentials are required?
None beyond access to the Docker daemon. Optional environment variables include DOCKER_HOST, DOCKER_NETWORK, and registry credentials like DOCKER_USERNAME (defaulting to $oauthtoken for NGC).
Install tao-run-on-local-docker
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nvidia/skills