Doca Container Deployment
NVIDIAOfficialCreated by NVIDIA
- Skill
- Workflow
- Cloud and DevOps
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured, cross-cutting runtime pattern for deploying DOCA services (such as Argus, DMS, Firefly, and UROM) as containers on BlueField DPU hardware. It focuses on the kubelet standalone agent workflow, where operators manage services by dropping YAML pod-spec files into a designated directory. The skill emphasizes a systematic, eight-layer error taxonomy for troubleshooting deployment failures and enforces a smoke-before-bulk safety policy to prevent uncontrolled restart loops. It acts as a loader for specific service configurations, ensuring consistent observability and lifecycle management across different DOCA services.
What it does
- Guides operators through the kubelet standalone deployment pattern for DOCA service containers.
- Provides a systematic eight-layer error taxonomy for diagnosing pod scheduling, image, and runtime issues.
- Enforces a smoke-before-bulk safety policy to ensure services are healthy before production use.
- Standardizes the inspection of pod status, ENTRYPOINT logs, and service-specific liveness signals.
- Routes per-service configuration and API-specific questions to their respective specialized skills.
- Coordinates with the BlueField OS environment to ensure proper deployment preconditions are met.
When to use it
- When deploying a packaged DOCA service container onto a BlueField DPU.
- When troubleshooting a pod that is stuck in Pending, ImagePullBackOff, or CrashLoopBackOff states.
- When verifying if a running container has successfully initialized its internal service.
- When managing service lifecycle events like restarts or configuration updates.
- When needing to determine if multiple DOCA services can coexist on a single BlueField target.
Advantages
- Provides a uniform deployment and debugging experience across all supported DOCA services.
- Reduces downtime by enforcing a structured diagnostic approach rather than trial-and-error.
- Prevents configuration drift by relying on documented patterns rather than manual ad-hoc changes.
- Ensures safety by prioritizing root-cause resolution over automated pod restarts.
- Clearly defines the boundary between general runtime operations and service-specific configurations.
Usage examples
- “How do I run a DOCA service container on my BlueField?”
- The agent identifies the target service, verifies the environment, and guides the user to drop the correct YAML pod-spec into the static-pod manifests directory.
- “My Firefly pod is in a restart loop after I edited the configuration. What should I do?”
- The agent halts the restart cycle, guides the user through the eight-layer error taxonomy to identify the specific configuration fault, and validates the fix before redeployment.
- “How can I check if the DMS service inside my container is actually ready?”
- The agent directs the user to the documented liveness signal and logs inspection procedure to confirm the service is fully operational.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/doca-container-deployment/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip doca-container-deployment.zip -d .agents/skills
Documentation by NVIDIA
DOCA container deployment
Examples
"How do I run a DOCA service container on BlueField?" — this is in scope after the setup recognize front door. Drop a documented pod spec; do not invent YAML or image tags.
"The pod spec is in the directory but the pod never starts." — walk the eight-layer taxonomy before letting kubelet restart-loop the pod.
Instructions
Follow Loading order below. Open the tasks companion for configure / run / debug. Open the capabilities companion for the kubelet-standalone contract. Do not open every companion file.
Where to start: This skill is for operating the cross-cutting DOCA container-deployment runtime — the shared pattern every DOCA service on the BlueField uses to come up (kubelet standalone agent on the BlueField Arm watching a static-pod manifests directory; the operator drops a YAML pod spec into that directory; kubelet schedules the pod and runs the container).
If the developer has NOT yet decided container vs. bare-metal
("I just got a BlueField, what now?", "my code is built, how do I
run it?", "how do I deploy this?"), route them BACK to
doca-setup/SKILL.md first.
That is the front-door routing decision. The wrong failure mode is
to silently push every developer onto the container path because the
agent loaded this skill first. ## recognize detects the system
shape, asks the minimum residual question, and lands the developer on
either this skill (when the workload is a packaged DOCA service to
drop on a BlueField) or the bare-metal-path sibling
doca-bare-metal-deployment/SKILL.md
(when the workload is a DOCA-linked application binary the developer
launches directly).
If the developer is already on the container path, open
the tasks companion and start at
## configure. If the question is what shape
of runtime is this and what does the deployment contract look like,
start at the capabilities companion. For per-service
overlays, follow the per-service skill under skills/services/ that
layers on top of this one — the supported overlays are Argus, DMS,
Firefly, and UROM service. Flow-Inspector and OS-Inspector are
outside this bundle's scope; route them through
doca-public-knowledge-map/SKILL.md
instead of applying this runtime overlay. Externally-productized
NVIDIA services (BlueMan, HBN, SNAP, Virtio-net, DOCA Telemetry
Service as productized, …) are also out of scope and route through
that map. If DOCA is
not installed on the BlueField target yet, route to
doca-setup/SKILL.md first.
Audience
This skill serves external operators and platform teams who deploy
DOCA service containers on BlueField — i.e., people who have a
BlueField with DOCA installed on the Arm side, a container runtime
plus the kubelet standalone agent already present per the BlueField
OS image, and the host-OS permissions the public DOCA Container
Deployment Guide names for the chosen service. The skill is the
shared deployment runtime; each per-service skill in the bundle
(see the list in ## Related skills) supplies
the service-specific config schema, paired-workload contract, and
"healthy" definition.
It is not for NVIDIA developers contributing to the BlueField
container runtime or to kubelet itself, and it is not a generic
Kubernetes tutorial. Kubelet runs on the BlueField in standalone
mode here — no full Kubernetes control plane, no kubectl against
a cluster API server — and the substantive answer to most
container-deployment questions on the BlueField is the public DOCA
Container Deployment Guide. This skill teaches the agent which
guide to quote, in what order to walk it, and how to map a symptom
to a layer; it does NOT re-invent kubelet flags, pod-spec field
names, or static-pod path strings. The shared deployment runtime
described here is the cross-cutting layer; the per-service skill
(doca-argus, doca-dms, doca-firefly,
doca-urom-svc) supplies the per-service
config schema, paired-workload contract, and "healthy" definition.
When to load this skill
Load this skill when the user is doing hands-on container deployment of any DOCA service on a BlueField target, or asking a cross-service deployment question that is not specific to one service's config schema. Concretely:
Dropping a YAML pod spec into the documented static-pod manifests directory on the BlueField Arm so kubelet standalone schedules the pod and runs the DOCA service container.
Inspecting pod status, container logs, and the documented liveness signal for any supported in-bundle DOCA service container — Argus, DMS, Firefly, or UROM service — so the agent answers "did the container come up, and is the service inside actually ready" the same way for every service.
Walking the smoke-before-bulk loop (pod reaches
Running; ENTRYPOINT logs are clean; service answers a trivial liveness probe) BEFORE the BlueField is put under workload.Diagnosing a deployment that is misbehaving — pod-spec YAML is in the directory but the pod never schedules; pod schedules but image-pull fails; image pulls but container ENTRYPOINT immediately exits; container runs but the service inside never answers; container is in a restart loop after a config edit; a volume mount the pod spec names is missing on the host; a network policy or host-firewall rule is blocking the service.
Cross-service questions: "can I have DMS and Firefly on the same BlueField", "how do I list every DOCA service pod that is currently running", "what is the documented stop / restart semantics if I edit a pod-spec file in place".
Do not load this skill for per-service config schema questions
(those belong to the matching per-service skill); for installing
DOCA itself or preparing the BlueField env (use
doca-setup/SKILL.md); for library-API
questions (use the matching libs/<library> skill); or for general
Kubernetes-cluster operations (this skill covers kubelet standalone
mode on the BlueField, not a full Kubernetes control plane).
What this skill provides
This is a thin loader. Substantive material lives in two companion files:
the capabilities companion — the cross-cutting DOCA container-deployment runtime contract on the BlueField (kubelet standalone agent on BlueField Arm watching a documented static-pod manifests directory; YAML pod-spec drop is the unit of operator input; the same pattern applies across every DOCA service), the BlueField preconditions (DOCA install, container runtime, BFB version, per-service firmware slot when the service emulates a device, image-pull reachability to NGC, host-OS permissions), the observability surface (kubelet status, container logs, service- side liveness signal — three layers, each with its own owner), the cross-cutting error taxonomy (pod-spec syntax → pod scheduling → image pull → runtime → volume mount → network policy → version → cross-cutting host) covering exactly eight layers, and the safety policy (smoke before bulk; failed pod is high-stakes — clear the root cause before letting kubelet restart-loop the pod; do NOT invent pod-spec field names / kubelet flags / image tags from memory).
the tasks companion — step-by-step workflows for the in-scope deployment verbs:
configure,build,modify,run,test,debug, plus aDeferred task verbsblock routing per-service config questions, host-firmware-slot work, paired-workload work, and full-Kubernetes-cluster work out to their owning skills.
The skill assumes a BlueField target where DOCA is already installed
on the Arm side, the BlueField OS image ships kubelet standalone +
the container runtime per the public DOCA Container Deployment
Guide, and the operator has the host-OS permissions that guide
names. It does not cover installing DOCA — that path goes through
doca-setup/SKILL.md — and it does not
re-document the per-service config schema, which is the canonical
concern of each DOCA service's public guide reached through
doca-public-knowledge-map/SKILL.md.
Loading order
Read this skill first to confirm the user's question is in scope (cross-cutting deployment runtime, NOT a per-service config-schema question).
For the kubelet-standalone-mode runtime shape, the static-pod manifests directory rule, the host-OS / BFB / firmware-slot / image-pull preconditions, the eight-layer error taxonomy, the observability surface, and the safety / smoke-before-bulk policy, see the capabilities companion.
For step-by-step workflows — configure, build, modify, run, test, debug — see the tasks companion.
Related skills
doca-public-knowledge-map/SKILL.md— public Container Deployment Guide, per-service guides, and NGC. Quote documented paths and tags from there; do not invent them.doca-setup/SKILL.md— env and install on the BlueField target, including the recognize front door that chooses this skill vs bare-metal.doca-bare-metal-deployment/SKILL.md— the sibling binary-launch path.doca-debug/SKILL.md— cross-cutting debug ladder this runtime's pod / image / ENTRYPOINT layers sit on.doca-version/SKILL.md— four-way match and container-tag overlay.doca-structured-tools-contract/SKILL.md— prefer structured status when present.Per-service overlays:
doca-argus/SKILL.md,doca-dms/SKILL.md,doca-firefly/SKILL.md,doca-urom-svc/SKILL.md.doca-programming-guide/SKILL.md— program-side discipline when a service surfaces a library error.
Files
- ATTRIBUTION.mdAdded by AutoGineer933 B
- BENCHMARK.md10.2 KiB
- CAPABILITIES.md29.9 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md10.8 KiB
- TASKS.md38.8 KiB
- evals/evals.json3.2 KiB
- references/details.md9.9 KiB
- skill-card.md4.8 KiB
- skill.oms.sig5.1 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
The author says: No DOCA install required to read this skill (it is an overlay loaded against any DOCA artifact skill); the validation steps within DO require a live DOCA install at /opt/mellanox/doca.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- NVIDIA
- Publisher
- NVIDIA (Official)
- Source
- NVIDIA/skills · skills/doca-container-deployment · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by NVIDIA or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download doca-container-deployment.zip