[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FSYV2WVF8X664YAZGGV2G":3,"skill-same:01M79FSYV2WVF8X664YAZGGV2G":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M79FSYV2WVF8X664YAZGGV2G","tao-run-on-local-docker",null,"Local Docker execution for TAO SDK job containers using the host Docker daemon and NVIDIA GPU runtime. Use when running TAO jobs on the current machine or a directly attached Docker host. Trigger phrases include \"run locally\", \"local Docker\", \"use my GPU\", \"run on my machine\", \"host Docker daemon\".","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Ftao-run-on-local-docker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: tao-run-on-local-docker\ndescription: Local Docker execution for TAO SDK job containers using the host Docker daemon and NVIDIA GPU runtime. Use\n  when running TAO jobs on the current machine or a directly attached Docker host. Trigger phrases include \"run locally\",\n  \"local Docker\", \"use my GPU\", \"run on my machine\", \"host Docker daemon\".\nlicense: Apache-2.0\ncompatibility: Requires NVIDIA driver branch 580, CUDA Toolkit 13.0, Docker, and NVIDIA Container Toolkit 1.19.0. The TAO SDK with the docker extra (pip install 'nvidia-tao-sdk[docker]') is needed only if you want Job handles, S3 I\u002FO wrapping, or run-folder durability via ActionWorkflow.\nmetadata:\n  author: NVIDIA Corporation\n  version: \"0.2.0\"\nallowed-tools: Read Bash\ntags:\n- platform\n- local\n- docker\n---\n\n# Local Docker\n\nSingle-node execution platform that runs TAO jobs as named Docker containers on\nthe local Docker daemon. It is useful for development, debugging, small runs,\nand machines where the agent host already has the required GPUs, NVIDIA driver,\nDocker, and NVIDIA Container Toolkit.\n\nUse local Docker when the data is local to the Docker host or accessible through\nmounted volumes\u002Fcloud credentials. Do not use it for remote cluster scheduling,\nmulti-node training, or jobs that need SLURM queueing.\n\n## Preflight\n\nThe workflow must verify the host GPU runtime before starting Docker jobs. If\nthe check fails, prompt the user to approve the install, run the printed install\ncommand, and rerun the preflight.\n\n```bash\n# Host GPU runtime: NVIDIA driver 580, CUDA 13.0, NVIDIA Container Toolkit 1.19.0.\nTAO_SKILL_BANK_ROOT=\"${TAO_SKILL_BANK_ROOT:-$PWD}\"\nSETUP_SCRIPT=\"${TAO_SKILL_BANK_ROOT}\u002Fskills\u002Ftao-setup-nvidia-gpu-host\u002Fscripts\u002Fsetup-nvidia-gpu-host.sh\"\n[ -x \"$SETUP_SCRIPT\" ] || SETUP_SCRIPT=\"${TAO_SKILL_BANK_ROOT}\u002Fplatform\u002Ftao-setup-nvidia-gpu-host\u002Fscripts\u002Fsetup-nvidia-gpu-host.sh\"\n\nbash \"$SETUP_SCRIPT\" --backend docker --check-only || {\n  echo \"MISSING: TAO GPU host runtime is not ready.\"\n  echo \"After user approval, run:\"\n  echo \"  bash \\\"$SETUP_SCRIPT\\\" --backend docker --install --yes\"\n  exit 1\n}\n\n# Mode 1 — direct docker (no Python). All you need is docker + the GPU runtime.\ndocker info >\u002Fdev\u002Fnull 2>&1 || { echo \"MISSING: docker daemon not reachable. Start Docker.\"; exit 1; }\ndocker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi >\u002Fdev\u002Fnull 2>&1 || {\n  echo \"MISSING: NVIDIA Container Toolkit not installed\u002Fconfigured. See:\"\n  echo \"  bash \\\"$SETUP_SCRIPT\\\" --backend docker --install --yes\"\n  exit 1\n}\n\n# Mode 2 — TAO SDK wrapper. Adds Job handles, S3 I\u002FO wrapping, ActionWorkflow.\n# Skip this block if Mode 1 is sufficient for the user's request.\n# When Mode 2 is in scope, read `tao-skill-bank:tao-run-platform` for the DockerSDK\n# kwarg contract, build_entrypoint, and monitoring patterns.\n# nvidia-tao-sdk is on public PyPI; pin lives in versions.yaml (wheels.tao_sdk_docker).\nPIN=$(\"${TAO_SKILL_BANK_PATH:?}\u002Fscripts\u002Fresolve_versions_key.py\" wheels.tao_sdk_docker)\npython -c \"import tao_sdk\" 2>\u002Fdev\u002Fnull || {\n  echo \"MISSING: nvidia-tao-sdk not installed. Run:\"\n  echo \"  pip install \\\"$PIN\\\"\"\n  exit 1\n}\npython -c \"import docker\" 2>\u002Fdev\u002Fnull || {\n  echo \"MISSING: docker Python client not installed. Run:\"\n  echo \"  pip install \\\"$PIN\\\"\"\n  exit 1\n}\n\n# DockerSDK attaches every job container to ${DOCKER_NETWORK:-tao_default}. If\n# the network does not exist, container start fails instantly with\n# `network \u003Cname> not found` for every create_job.\nDOCKER_NETWORK_NAME=\"${DOCKER_NETWORK:-tao_default}\"\ndocker network ls --format '{{.Name}}' | grep -qx \"$DOCKER_NETWORK_NAME\" || {\n  echo \"MISSING: docker network '$DOCKER_NETWORK_NAME' not found. After user approval, run:\"\n  echo \"  docker network create $DOCKER_NETWORK_NAME\"\n  exit 1\n}\n```\n\nIf a check fails, the agent prompts the user to authorize the install\u002Ffix via Bash before proceeding.\n\n## Credentials\n\nThere are no platform credentials required beyond access to the Docker daemon.\n\nOptional environment:\n\n- **DOCKER_HOST**: Optional Docker daemon URL. If unset, the SDK uses the\n  Docker Python client's normal environment\u002Fdefault socket resolution.\n- **DOCKER_NETWORK**: Docker network for job containers. Default is\n  `tao_default`.\n- **DOCKER_USERNAME**: Registry username. Default is `$oauthtoken` for NGC.\n- **NGC_KEY**: Used when pulling private images from `nvcr.io`.\n- **HOST_SSH_PATH**: Mounted into AutoML brain containers when they need SSH keys\n  to monitor remote SLURM child jobs.\n- **ACCESS_KEY**, **SECRET_KEY**, **S3_ENDPOINT_URL**, **S3_BUCKET_NAME**:\n  Optional S3-compatible storage settings for jobs that still read\u002Fwrite cloud\n  storage from a local container.\n\n## Launch Preflight\n\nBefore generating scripts or starting containers:\n\n1. Verify the Docker daemon is reachable and the NVIDIA runtime can see GPUs.\n2. Verify every local\u002Ffile dataset annotation and media path exists on the\n   Docker host.\n3. For `s3:\u002F\u002F` datasets\u002Fresults, verify `ACCESS_KEY` and `SECRET_KEY` are set\n   and the exact paths are readable with `aws s3 ls`.\n4. Verify model-specific credentials such as `HF_TOKEN` before launch.\n\n## Multi-GPU and multi-node\n\n**Multi-node is not supported on local Docker.** One job runs on the local Docker daemon's host with no cross-host coordination.\n\nMulti-GPU **on the local host** is supported via the NVIDIA Container Toolkit's `--gpus` flag (`--gpus all` or `--gpus '\"device=0,1,2,3\"'`). `DockerSDK.create_job(gpu_count=N)` plumbs through to `--gpus`. Single-host distributed init uses `localhost`; `torchrun --nproc-per-node=N` or PyTorch DDP work as usual.\n\n## Backend Details\n\nUse the SDK backend value `local-docker`. The local backend schema has no extra\nbackend details, so most routing is controlled by environment and job\nparameters:\n\n```json\n{\n  \"backend_type\": \"local-docker\",\n  \"num_gpu\": 1\n}\n```\n\nFollowing the Lepton\u002FBrev SDK design, platform\u002Fcontrol-plane values stay in SDK\nstate and Docker labels. The SDK does not inject `BACKEND`, `HOST_PLATFORM`,\n`MONGOSECRET`, `DOCKER_HOST`, or `DOCKER_NETWORK` into the training container.\n\n## Container Execution\n\nThe TAO SDK local Docker handler starts containers through the Docker Python\nclient:\n\n- Backend job name uses the `tao-job-\u003Cjob_id>` form used by SDK handlers.\n- Command is usually `[\"\u002Fbin\u002Fbash\", \"-c\", \"\u003Cjob command>\"]`.\n- Containers run detached. The SDK keeps containers by default so status and\n  logs remain inspectable, unless `DOCKER_AUTO_REMOVE=true`.\n- `\u002Fdev\u002Fshm` is mounted as tmpfs.\n- The configured Docker network is applied by the Docker daemon for the job\n  container; it is not passed through as a process environment variable.\n- Existing containers with the same job id are stopped and removed before a\n  replacement starts.\n\nFor GPU access, the handler auto-detects the host type:\n\n- Tegra or Jetson hosts use `runtime=\"nvidia\"` plus\n  `NVIDIA_VISIBLE_DEVICES` and `NVIDIA_DRIVER_CAPABILITIES=all`.\n- Standard x86 hosts use Docker `device_requests` with GPU capabilities.\n\nIf `num_gpus` is `0`, no GPUs are assigned. If `num_gpus` is `-1`, all visible\nGPUs are requested. Prefer explicit GPU counts for shared development machines.\n\n## Storage\n\nLocal Docker accepts local and `file:\u002F\u002F` paths because the container runs on the\nsame Docker host. Make sure every path in the spec is either:\n\n- mounted into the container by the handler or surrounding service,\n- reachable from inside the container already, or\n- a cloud URI with matching credentials.\n\nFor remote\u002Fshared filesystems, prefer the platform that owns that filesystem.\nFor example, use SLURM plus `lustre:\u002F\u002F\u002F...` for Lustre paths on a cluster.\n\n## Monitoring\n\n- The SDK handler maps Docker container state directly: created -> Pending,\n  running\u002Frestarting -> Running, paused -> Paused, exit code 0 -> Complete,\n  nonzero exit -> Error.\n- Logs come directly from the named container through the Docker Python client\n  (`docker logs tao-job-\u003Cjob_id>`).\n\nIf the container has exited, died, is being removed, or cannot be found, status\nreconciliation treats the backend process as terminated.\n\n## Cancellation\n\nCancellation stops the named container. GPU ownership is managed by Docker \u002F\nthe NVIDIA runtime, not by TAO Core's local GPU manager.\n\n## Optional: via the TAO SDK\n\nIf you want Job handles, S3 I\u002FO wrapping via the SDK's `script_runner`, or\ndurability across sessions:\n\n```python\nfrom tao_sdk.platforms.docker import DockerSDK\n\nsdk = DockerSDK()  # reads DOCKER_HOST, NGC_KEY, S3 creds from env\njob = sdk.create_job(\n    image='nvcr.io\u002Fnvidia\u002Ftao\u002Ftao-toolkit:6.26.3-pyt',\n    command='dino train -e \u002Ftmp\u002Fspec.yaml',\n    gpu_count=1,\n    inputs={'\u002Fdata\u002Ftrain.json': 's3:\u002F\u002Fbucket\u002Fcoco\u002Ftrain.json'},\n    outputs=['\u002Fresults\u002F'],\n)\n\nstatus = sdk.get_job_status(job.id)\nlogs = sdk.get_job_logs(job.id, tail=200)\n```\n\nThis wraps the same `docker run` invocation under a `Job` handle and routes\nthe entrypoint through `script_runner` so `inputs`\u002F`outputs` get downloaded\nfrom \u002F uploaded to S3 automatically. If you don't need those, just use\n`docker run` directly — no SDK install required.\n\n## Failure Modes\n\n**Docker client not initialized**: Verify the Docker Python package is installed,\nset `DOCKER_HOST` if you are not using the default local socket, and confirm the\nprocess can talk to the daemon.\n\n**GPU assignment failed**: Requested GPUs are unavailable, the NVIDIA Container\nToolkit is not configured, or the Docker daemon cannot create GPU device\nrequests. Use fewer GPUs, wait for another job to finish, or verify\n`docker run --gpus ...` works on the host.\n\n**Image pull auth failed**: Set a valid `NGC_KEY` for private `nvcr.io` images\nor run `docker login nvcr.io -u '$oauthtoken'` on the Docker host.\n\n**Container exited unexpectedly**: Check `docker logs tao-job-\u003Cjob_id>`, the\nconfigured `DOCKER_NETWORK`, and the command produced by the SDK action runner.\n\n**Path missing inside container**: A local path on the host is not necessarily\nmounted into the job container. Use a path convention supported by the action\nrunner or configure an explicit volume through the surrounding service.\n","# Local Docker\n\nSingle-node execution platform that runs TAO jobs as named Docker containers on\nthe local Docker daemon. It is useful for development, debugging, small runs,\nand machines where the agent host already has the required GPUs, NVIDIA driver,\nDocker, and NVIDIA Container Toolkit.\n\nUse local Docker when the data is local to the Docker host or accessible through\nmounted volumes\u002Fcloud credentials. Do not use it for remote cluster scheduling,\nmulti-node training, or jobs that need SLURM queueing.\n\n## Preflight\n\nThe workflow must verify the host GPU runtime before starting Docker jobs. If\nthe check fails, prompt the user to approve the install, run the printed install\ncommand, and rerun the preflight.\n\n```bash\n# Host GPU runtime: NVIDIA driver 580, CUDA 13.0, NVIDIA Container Toolkit 1.19.0.\nTAO_SKILL_BANK_ROOT=\"${TAO_SKILL_BANK_ROOT:-$PWD}\"\nSETUP_SCRIPT=\"${TAO_SKILL_BANK_ROOT}\u002Fskills\u002Ftao-setup-nvidia-gpu-host\u002Fscripts\u002Fsetup-nvidia-gpu-host.sh\"\n[ -x \"$SETUP_SCRIPT\" ] || SETUP_SCRIPT=\"${TAO_SKILL_BANK_ROOT}\u002Fplatform\u002Ftao-setup-nvidia-gpu-host\u002Fscripts\u002Fsetup-nvidia-gpu-host.sh\"\n\nbash \"$SETUP_SCRIPT\" --backend docker --check-only || {\n  echo \"MISSING: TAO GPU host runtime is not ready.\"\n  echo \"After user approval, run:\"\n  echo \"  bash \\\"$SETUP_SCRIPT\\\" --backend docker --install --yes\"\n  exit 1\n}\n\n# Mode 1 — direct docker (no Python). All you need is docker + the GPU runtime.\ndocker info >\u002Fdev\u002Fnull 2>&1 || { echo \"MISSING: docker daemon not reachable. Start Docker.\"; exit 1; }\ndocker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi >\u002Fdev\u002Fnull 2>&1 || {\n  echo \"MISSING: NVIDIA Container Toolkit not installed\u002Fconfigured. See:\"\n  echo \"  bash \\\"$SETUP_SCRIPT\\\" --backend docker --install --yes\"\n  exit 1\n}\n\n# Mode 2 — TAO SDK wrapper. Adds Job handles, S3 I\u002FO wrapping, ActionWorkflow.\n# Skip this block if Mode 1 is sufficient for the user's request.\n# When Mode 2 is in scope, read `tao-skill-bank:tao-run-platform` for the DockerSDK\n# kwarg contract, build_entrypoint, and monitoring patterns.\n# nvidia-tao-sdk is on public PyPI; pin lives in versions.yaml (wheels.tao_sdk_docker).\nPIN=$(\"${TAO_SKILL_BANK_PATH:?}\u002Fscripts\u002Fresolve_versions_key.py\" wheels.tao_sdk_docker)\npython -c \"import tao_sdk\" 2>\u002Fdev\u002Fnull || {\n  echo \"MISSING: nvidia-tao-sdk not installed. Run:\"\n  echo \"  pip install \\\"$PIN\\\"\"\n  exit 1\n}\npython -c \"import docker\" 2>\u002Fdev\u002Fnull || {\n  echo \"MISSING: docker Python client not installed. Run:\"\n  echo \"  pip install \\\"$PIN\\\"\"\n  exit 1\n}\n\n# DockerSDK attaches every job container to ${DOCKER_NETWORK:-tao_default}. If\n# the network does not exist, container start fails instantly with\n# `network \u003Cname> not found` for every create_job.\nDOCKER_NETWORK_NAME=\"${DOCKER_NETWORK:-tao_default}\"\ndocker network ls --format '{{.Name}}' | grep -qx \"$DOCKER_NETWORK_NAME\" || {\n  echo \"MISSING: docker network '$DOCKER_NETWORK_NAME' not found. After user approval, run:\"\n  echo \"  docker network create $DOCKER_NETWORK_NAME\"\n  exit 1\n}\n```\n\nIf a check fails, the agent prompts the user to authorize the install\u002Ffix via Bash before proceeding.\n\n## Credentials\n\nThere are no platform credentials required beyond access to the Docker daemon.\n\nOptional environment:\n\n- **DOCKER_HOST**: Optional Docker daemon URL. If unset, the SDK uses the\n  Docker Python client's normal environment\u002Fdefault socket resolution.\n- **DOCKER_NETWORK**: Docker network for job containers. Default is\n  `tao_default`.\n- **DOCKER_USERNAME**: Registry username. Default is `$oauthtoken` for NGC.\n- **NGC_KEY**: Used when pulling private images from `nvcr.io`.\n- **HOST_SSH_PATH**: Mounted into AutoML brain containers when they need SSH keys\n  to monitor remote SLURM child jobs.\n- **ACCESS_KEY**, **SECRET_KEY**, **S3_ENDPOINT_URL**, **S3_BUCKET_NAME**:\n  Optional S3-compatible storage settings for jobs that still read\u002Fwrite cloud\n  storage from a local container.\n\n## Launch Preflight\n\nBefore generating scripts or starting containers:\n\n1. Verify the Docker daemon is reachable and the NVIDIA runtime can see GPUs.\n2. Verify every local\u002Ffile dataset annotation and media path exists on the\n   Docker host.\n3. For `s3:\u002F\u002F` datasets\u002Fresults, verify `ACCESS_KEY` and `SECRET_KEY` are set\n   and the exact paths are readable with `aws s3 ls`.\n4. Verify model-specific credentials such as `HF_TOKEN` before launch.\n\n## Multi-GPU and multi-node\n\n**Multi-node is not supported on local Docker.** One job runs on the local Docker daemon's host with no cross-host coordination.\n\nMulti-GPU **on the local host** is supported via the NVIDIA Container Toolkit's `--gpus` flag (`--gpus all` or `--gpus '\"device=0,1,2,3\"'`). `DockerSDK.create_job(gpu_count=N)` plumbs through to `--gpus`. Single-host distributed init uses `localhost`; `torchrun --nproc-per-node=N` or PyTorch DDP work as usual.\n\n## Backend Details\n\nUse the SDK backend value `local-docker`. The local backend schema has no extra\nbackend details, so most routing is controlled by environment and job\nparameters:\n\n```json\n{\n  \"backend_type\": \"local-docker\",\n  \"num_gpu\": 1\n}\n```\n\nFollowing the Lepton\u002FBrev SDK design, platform\u002Fcontrol-plane values stay in SDK\nstate and Docker labels. The SDK does not inject `BACKEND`, `HOST_PLATFORM`,\n`MONGOSECRET`, `DOCKER_HOST`, or `DOCKER_NETWORK` into the training container.\n\n## Container Execution\n\nThe TAO SDK local Docker handler starts containers through the Docker Python\nclient:\n\n- Backend job name uses the `tao-job-\u003Cjob_id>` form used by SDK handlers.\n- Command is usually `[\"\u002Fbin\u002Fbash\", \"-c\", \"\u003Cjob command>\"]`.\n- Containers run detached. The SDK keeps containers by default so status and\n  logs remain inspectable, unless `DOCKER_AUTO_REMOVE=true`.\n- `\u002Fdev\u002Fshm` is mounted as tmpfs.\n- The configured Docker network is applied by the Docker daemon for the job\n  container; it is not passed through as a process environment variable.\n- Existing containers with the same job id are stopped and removed before a\n  replacement starts.\n\nFor GPU access, the handler auto-detects the host type:\n\n- Tegra or Jetson hosts use `runtime=\"nvidia\"` plus\n  `NVIDIA_VISIBLE_DEVICES` and `NVIDIA_DRIVER_CAPABILITIES=all`.\n- Standard x86 hosts use Docker `device_requests` with GPU capabilities.\n\nIf `num_gpus` is `0`, no GPUs are assigned. If `num_gpus` is `-1`, all visible\nGPUs are requested. Prefer explicit GPU counts for shared development machines.\n\n## Storage\n\nLocal Docker accepts local and `file:\u002F\u002F` paths because the container runs on the\nsame Docker host. Make sure every path in the spec is either:\n\n- mounted into the container by the handler or surrounding service,\n- reachable from inside the container already, or\n- a cloud URI with matching credentials.\n\nFor remote\u002Fshared filesystems, prefer the platform that owns that filesystem.\nFor example, use SLURM plus `lustre:\u002F\u002F\u002F...` for Lustre paths on a cluster.\n\n## Monitoring\n\n- The SDK handler maps Docker container state directly: created -> Pending,\n  running\u002Frestarting -> Running, paused -> Paused, exit code 0 -> Complete,\n  nonzero exit -> Error.\n- Logs come directly from the named container through the Docker Python client\n  (`docker logs tao-job-\u003Cjob_id>`).\n\nIf the container has exited, died, is being removed, or cannot be found, status\nreconciliation treats the backend process as terminated.\n\n## Cancellation\n\nCancellation stops the named container. GPU ownership is managed by Docker \u002F\nthe NVIDIA runtime, not by TAO Core's local GPU manager.\n\n## Optional: via the TAO SDK\n\nIf you want Job handles, S3 I\u002FO wrapping via the SDK's `script_runner`, or\ndurability across sessions:\n\n```python\nfrom tao_sdk.platforms.docker import DockerSDK\n\nsdk = DockerSDK()  # reads DOCKER_HOST, NGC_KEY, S3 creds from env\njob = sdk.create_job(\n    image='nvcr.io\u002Fnvidia\u002Ftao\u002Ftao-toolkit:6.26.3-pyt',\n    command='dino train -e \u002Ftmp\u002Fspec.yaml',\n    gpu_count=1,\n    inputs={'\u002Fdata\u002Ftrain.json': 's3:\u002F\u002Fbucket\u002Fcoco\u002Ftrain.json'},\n    outputs=['\u002Fresults\u002F'],\n)\n\nstatus = sdk.get_job_status(job.id)\nlogs = sdk.get_job_logs(job.id, tail=200)\n```\n\nThis wraps the same `docker run` invocation under a `Job` handle and routes\nthe entrypoint through `script_runner` so `inputs`\u002F`outputs` get downloaded\nfrom \u002F uploaded to S3 automatically. If you don't need those, just use\n`docker run` directly — no SDK install required.\n\n## Failure Modes\n\n**Docker client not initialized**: Verify the Docker Python package is installed,\nset `DOCKER_HOST` if you are not using the default local socket, and confirm the\nprocess can talk to the daemon.\n\n**GPU assignment failed**: Requested GPUs are unavailable, the NVIDIA Container\nToolkit is not configured, or the Docker daemon cannot create GPU device\nrequests. Use fewer GPUs, wait for another job to finish, or verify\n`docker run --gpus ...` works on the host.\n\n**Image pull auth failed**: Set a valid `NGC_KEY` for private `nvcr.io` images\nor run `docker login nvcr.io -u '$oauthtoken'` on the Docker host.\n\n**Container exited unexpectedly**: Check `docker logs tao-job-\u003Cjob_id>`, the\nconfigured `DOCKER_NETWORK`, and the command produced by the SDK action runner.\n\n**Path missing inside container**: A local path on the host is not necessarily\nmounted into the job container. Use a path convention supported by the action\nrunner or configure an explicit volume through the surrounding service.\n",{"name":5,"tags":24,"license":15,"metadata":28,"description":7,"allowed-tools":31,"compatibility":32},[25,26,27],"platform","local","docker",{"author":29,"version":30},"NVIDIA Corporation","0.2.0","Read Bash","Requires NVIDIA driver branch 580, CUDA Toolkit 13.0, Docker, and NVIDIA Container Toolkit 1.19.0. The TAO SDK with the docker extra (pip install 'nvidia-tao-sdk[docker]') is needed only if you want Job handles, S3 I\u002FO wrapping, or run-folder durability via ActionWorkflow.","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","skills\u002Fnvidia\u002Ftao-run-on-local-docker","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill tao-run-on-local-docker",{"tool":45,"command":46},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill tao-run-on-local-docker",{"tool":48,"command":49},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill tao-run-on-local-docker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Ftao-run-on-local-docker\u002FSKILL.md",true,[53,59,63,67,71],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"BENCHMARK.md","REFERENCE","参考文档",4340,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Ftao-run-on-local-docker\u002FBENCHMARK.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"evals\u002Fevals.json",791,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Ftao-run-on-local-docker\u002Fevals\u002Fevals.json",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fskill_info.yaml",833,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Ftao-run-on-local-docker\u002Freferences\u002Fskill_info.yaml",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"skill-card.md",3631,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Ftao-run-on-local-docker\u002Fskill-card.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"skill.oms.sig","OTHER","其他",4837,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Ftao-run-on-local-docker\u002Fskill.oms.sig",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]