cosmos3-env-troubleshoot

por nvidia

Diagnosticar e corrigir erros de ambiente, instalação e tempo de execução do Cosmos3. Use quando o usuário encontrar um ImportError, ModuleNotFoundError, erro de CUDA, Docker…

npx skills add https://github.com/nvidia/cosmos-framework --skill cosmos3-env-troubleshoot

Cosmos3 Environment Troubleshooting

When to use this skill

  • Use when a user hits an error during installation, environment setup, or first run
  • Use when a traceback mentions torch, CUDA, missing modules, or shared libraries
  • Use when Docker or container setup fails
  • Use when checkpoint downloads fail or HuggingFace auth errors appear

Path convention

All paths below are relative to this file's location (.agents/skills/cosmos3-env-troubleshoot/).

Step 1: Match against known errors

Check the error message against the table below. Each row links to the canonical fix in the docs.

Error signatureCauseFix location
ImportError: cannot import name '_functionalization' from 'torch._C'NGC container library conflict../../../docs/setup.md § PyTorch Import Issue — run export LD_LIBRARY_PATH=''
ModuleNotFoundError: No module named 'cosmos_framework'Package not installed../../../docs/setup.md § Dependency Issue — run uv sync --all-extras --group=cu130-train --reinstall
ModuleNotFoundError: No module named <other>Dependency missing../../../docs/setup.md § Dependency Issue — reinstall venv
fatal error: Python.h: No such file or directoryBroken Python / uv install../../../docs/setup.md § Python Issue — reinstall uv + venv from scratch
OSError: <lib>: cannot open shared object fileCUDA version mismatch../../../docs/setup.md § CUDA Issue — install matching cuda-toolkit-<major>
docker: Error response from daemon: unknown or invalid runtime name: nvidiaDocker nvidia runtime not configured../../../docs/setup.md § Docker Container — run sudo nvidia-ctk runtime configure --runtime=docker
HuggingFace 401 / download failuresAuth or license not accepted../../../docs/setup.md § Downloading Base Checkpoints — check HF_TOKEN, accept license agreement

Step 2: If no documented fix matches, try common remediation

Run these diagnostic commands to collect information, then attempt fixes in order:

Diagnostic commands

# System
uname -a
cat /etc/os-release | head -5

# Python
python --version
which python

# CUDA
nvidia-smi
python -c "import torch; print(f'torch={torch.__version__}, cuda={torch.version.cuda}')"

# Package
uv pip list | head -20

Remediation ladder (try in order)

  1. Clear library path: export LD_LIBRARY_PATH=''

  2. Reinstall venv: uv sync --all-extras --group=cu130-train --reinstall (or cu128-train on older drivers; drop -train only if you intentionally want the inference-only group)

  3. Reinstall uv + venv from scratch:

    curl -LsSf https://astral.sh/uv/install.sh | sh
    uv python install --reinstall
    rm -rf .venv
    uv sync --all-extras --group=cu130-train --reinstall
    source .venv/bin/activate
    
  4. Check CUDA version alignment: the major CUDA version from nvidia-smi must match torch.version.cuda

  5. Try Docker: if the host environment is too broken, fall back to the Docker container (see ../../../docs/setup.md)

Step 3: If still unresolved, generate a bug report

If none of the above resolves the issue, collect environment information and present the user with a pre-filled bug report they can submit as a GitHub issue.

Fill in the template below by running the diagnostic commands and inserting the results:

## Environment

- **OS**: <output of `uname -a`>
- **Python**: <output of `python --version`>
- **CUDA (system)**: <output of `nvidia-smi` — first line with driver/CUDA version>
- **CUDA (torch)**: <output of `python -c "import torch; print(torch.version.cuda)">`>
- **torch version**: <output of `python -c "import torch; print(torch.__version__)">`>
- **cosmos_framework version**: <output of `python -c "import cosmos_framework; print(cosmos_framework.__version__)"` or "not installed">
- **Installation method**: <uv sync / uv pip / Docker / NGC container>

## Error

```
<full traceback>
```

## What was tried

1. <list each remediation step attempted and its result>

## Additional context

<any other relevant details — multi-GPU setup, custom CUDA install, etc.>

Mais skills de nvidia

fhir-basics
nvidia
Ensina aos agentes como funcionam as APIs FHIR R4, quais recursos estão disponíveis, como consultá-los com parâmetros de busca e como analisar corretamente todos os formatos de resposta…
compileiq-validate-result
nvidia
Use APÓS a conclusão de uma Pesquisa e ANTES de reivindicar qualquer aceleração ou enviar um ACF. Carrega o CSV dump_results, extrai os K melhores candidatos (objetivo único)…
changelog-audit
nvidia
Auditar o CHANGELOG.md do Warp antes de um lançamento: recuperar entradas perdidas, ordenar por impacto ao usuário, refinar a linguagem das entradas, ajustar quebras de linha e (no modo de branch de lançamento) incrementar comparação…
dgx-diagnose
nvidia
Diagnostique problemas comuns do DGX Station GB300 — falhas de CUDA, direcionamento incorreto de GPU, bugs de contêiner vLLM/SGLang, problemas de estado MIG, erros de NVLink/Fabric Manager,…
aicr-managing-openvex
nvidia
Use when adding, updating, or removing CVE/GHSA suppressions in `.openvex.json` — the OpenVEX document consumed by the daily image vulnerability scan workflow.…
aicr-creating-slide-decks
nvidia
Use ao criar um deck de slides HTML autocontido ou um ponto visual de discussão para um conceito técnico ou fluxo de trabalho (ex.: demos/*.html) — exibido em tela cheia ou…
aicr-creating-guided-demos
nvidia
Estrutura um script de demonstração guiada interativa (demos/*.sh), ao vivo ou no ritmo do usuário, com o padrão Frame → Tell → Show → Close. Aciona em "demo script", "guided…
aicr-analyzing-snapshots
nvidia
Use ao analisar um arquivo YAML de snapshot AICR, revisando o estado do cluster, comparando características de provedores, extraindo insights de topologia de GPU/rede, ou…