doca-upgrade

Guides confirmation-gated DOCA upgrades, downgrades, and failed-upgrade recovery on BlueField hosts.

3.2k|370|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/NVIDIA/skills --skill doca-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doca-upgrade
Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-upgrade
Command: npx skills add https://github.com/NVIDIA/skills --skill doca-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading or downgrading NVIDIA DOCA across host packages, BlueField BFB images, and NGC container tags is risky: partial upgrades, apt-source drift, and host/BFB version skew can leave systems in a broken state. This Skill enforces a detect → report → ASK → only-then guided upgrade discipline so no upgrade command ever runs without explicit user confirmation.

Core Features & Use Cases

  • Gap detection and reporting: Detects the installed DOCA release (via doca-version), discovers the current target release from public release notes, and reports the installed → target gap before any action.
  • Confirmation-gated guided upgrades: Walks host apt upgrades, BFB reflashes, container tag bumps, and rollbacks only after explicit confirmation, with rollback-first and maintenance-window gates.
  • Failed-upgrade recovery: Diagnoses partial upgrades, aborted dpkg transactions, apt-source drift, and host/BFB skew through a documented recovery ladder.
  • Use Case: A user on DOCA 3.1.0 asks whether a newer release exists and how to move safely. The Skill detects the installed version, reports the gap and cost, then stops and waits for explicit confirmation before any upgrade step.

Quick Start

Ask your agent: "I'm on DOCA 3.1.0 — is there a newer release, and how do I move to it safely?"

The agent will load this Skill, detect the installed version, report the gap, and wait for your confirmation before proposing any upgrade command.

Frequently Asked Questions about doca-upgrade

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

FAQPage Schema
How do I safely upgrade DOCA to a newer release?

Follow the detect → report → ASK → guided upgrade discipline: detect the installed version, discover the current target from the DOCA release notes, report the gap, then confirm explicitly before any command runs. Hardware, firmware, and reboot steps are delegated to the doca-hardware-safety skill.

How do I recover from a failed or partial DOCA upgrade?

Capture the four-source version state, classify the failure against the error taxonomy (partial upgrade, apt-source drift, host/BFB skew, aborted dpkg transaction), then apply the single documented corrective action and re-verify with the four-way version match.

Does this skill handle first-time DOCA installation?

No. First-time installation is owned by the doca-setup skill. This skill only covers moving between already-installed DOCA releases, including upgrades, downgrades, BFB reflashes, and container tag bumps.

Can I upgrade DOCA across any two versions?

Only if the installed → target jump is documented in the NVIDIA DOCA Compatibility Policy and target release notes. Unsupported jumps fail closed: the skill reports them as unsupported rather than inventing intermediate release steps.

Why does my host show a different DOCA version than my BlueField after upgrading?

This is host/BFB version skew: the host packages moved but the BFB image did not. The missing step is a BFB reflash, which is delegated to doca-hardware-safety, followed by re-verification of the four-way version match.