skills.rest
NVIDIA
NVIDIAOFFICIAL
Explore all skills by this author →
WebsiteGitHub

doca-version

Detects and validates DOCA version consistency across pkg-config, install tree, runtime, and BlueField BFB sources.

3.2k|370|Updated Feb 25, 2026
Search Tags:#compatibility#Debugging#NVIDIA#doca#bluefield#version detection#pkg-config
One-click install
npx skills add https://github.com/NVIDIA/skills --skill doca-version
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doca-version
Source: https://github.com/NVIDIA/skills/tree/main/skills/doca-version
Command: npx skills add https://github.com/NVIDIA/skills --skill doca-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DOCA installs can silently drift: build-time headers, runtime libraries, install-tree files, and BlueField BFB images may come from different releases, causing confusing failures like programs that build fine but do nothing on the wire. This Skill gives agents a canonical detection chain and four-way match rule to detect the installed DOCA release, validate consistency, and diagnose version drift instead of guessing versions from memory.

Core Features & Use Cases

  • Four-source version detection: Walks pkg-config doca-common, /opt/mellanox/doca/applications/VERSION, doca_caps --version, and bfver plus /etc/mlnx-release on BlueField hosts, with a structured doca-env --json shortcut when available.
  • Partial-install and drift diagnosis: Maps symptoms like DOCA_ERROR_NOT_SUPPORTED at runtime or missing pkg-config modules to specific version-mismatch root causes and routes fixes to the right skill.
  • Capability availability lookup: Checks whether a DOCA capability exists on the installed release via a version-matrix lookup with fallback to per-library documentation.
  • Use Case: A user reports their DOCA program compiled successfully but fails at runtime. The agent runs the four-source chain, finds pkg-config reports 3.3.0 while doca_caps reports 3.2.0, identifies a build-vs-runtime partial install, and routes to a consistent reinstall.

Quick Start

Ask the agent what DOCA version is installed on this host and whether the install is consistent across all sources.

Frequently Asked Questions about doca-version

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

FAQPage Schema
How do I check which DOCA version is installed on my host?▼

Run the four-source detection chain: pkg-config --modversion doca-common, cat /opt/mellanox/doca/applications/VERSION, doca_caps --version, and on BlueField hosts bfver plus cat /etc/mlnx-release. All sources must agree for the install to be consistent.

Why does my DOCA program build fine but fail at runtime?▼

This is the canonical build-vs-runtime drift symptom: the headers you compiled against are from one DOCA release while the runtime shared libraries are from another. Check pkg-config --modversion doca-common against doca_caps --version and inspect ldconfig -p for multiple installs.

How do I check if a DOCA capability is available on my installed version?▼

Look up the capability's minimum DOCA version in version-matrix.json if present, otherwise fetch the per-library documentation page and extract the available-since statement. Then confirm at runtime with the matching doca_<library>_cap_* query, which overrides the matrix when they disagree.

Does DOCA version handling work inside the NGC container?▼

Yes, but the four-way match applies to the container itself since headers, libraries, samples, and doca_caps ship together at the pulled tag. Verify with pkg-config --variable=prefix doca-common and ldd that no host-mounted DOCA libraries contaminate the container.

When should I use doca-setup instead of doca-version?▼

Use doca-setup for installing DOCA, choosing packages, and post-install verification. doca-version assumes something is already installed and answers what was installed and whether it is consistent; it routes all install procedures to doca-setup.

Related Skills

Explore More Software Engineering Skills→
air-gappedair-gapped
5

nvidia-datacenter-bringup

Automate NVIDIA datacenter GPU bring-up on Ubuntu 24.04 with health validation.

Official
Advanced
LazyIsEfficientLazyIsEfficient
15

debugging-and-error-recovery

Diagnoses failures through structured reproduction, localization, and root-cause verification.

Official
Advanced
samymitysamymity
1

documentation-lookup

Fetch current Context7 documentation for named libraries and frameworks.

Community
Intermediate
InnerScopeHearingInnerScopeHearing

sunset-protocol

Transfer an agent's state and memory between engines with ring safety.

Official
Advanced