xpu-container-run SKILL.md skillA
xpu-container-run from intel/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add intel/skills/xpu-container-run@git:20261105.f0386a9Pins git:20261105.f0386a9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- intel/skills
- Path
skills/xpu-container-run/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261105.f0386a9, committed Nov 5, 2026
- First version recorded
- Sep 3, 2026
- Size
- 6,403 bytes
- Repository stars
- 29
- License
- Apache-2.0
Launch a Docker container with Intel GPU access on Linux. Encodes the correct combination of `--device /dev/dri`, render-group access, `--ipc=host`, `ZE_AFFINITY_MASK` pinning, Hugging Face cache mount, and `--entrypoint /bin/bash` for interactive use. Use when running any Intel-XPU container (vLLM-XPU, sglang-xpu, torch-XPU, llama.cpp SYCL, etc.) and the device must be visible inside. The CUDA analogue is `docker run --gpus all` — Intel has no `--gpus` flag, you pass the Direct Rendering…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# xpu-container-run Intel GPUs do not plug into Docker via `--gpus all`. There is no `nvidia-container-toolkit` equivalent. Pass the kernel's Direct Rendering Manager (DRM) character devices into the container and grant the right group ownership. ## CUDA → Intel cheat sheet | CUDA | Intel | |---|---| | `docker run --gpus all` | `--device /dev/dri --group-add "$(getent group render \| cut -d: -f3)"` | | `docker run --gpus '"device=0"'` | `-e ZE_AFFINITY_MASK=0` | | `--ipc=host` | same | | `--shm-size=16g` | same (alternative to `--ipc=host`) | | `--runtime nvidia` | nothing — `xe`/`i915` is in-kernel | | `nvidia-smi` inside container | `xpu-smi discovery` | No "Intel container toolkit" needed; passing the DRM nodes is enough. ## Image source Comes from the runner skill: - vLLM serving → **vllm-xpu-run** (`vllm/vllm-openai-xpu:latest`) - SGLang → **sglang-xpu-run** (`lmsysorg/sglang:v<version>-xpu`; that skill pins a validated tag — there is no `latest-xpu`) - PyTorch / Transformers → **torch-xpu-run** `<image>` below is whichever you picked. ## Quickstart — interactive shell, one GPU Confirm the image name with the user before running — this binds …
Read the whole file at its exact version.
How to install
mdr add intel/skills/xpu-container-run@sha256:543b24fcc905dee4The line at the top of this page pins the label git:20261105.f0386a9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_q522gytpdrwbf2tw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 3, 2026 and Nov 5, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261105.f0386a9 latest | 2026-11-05 | f0386a9 | 6,403 B | A | view · diff |
| git:20261012.557ee81 | 2026-10-12 | 557ee81 | 5,718 B | A | view · diff |
| git:20260924.04b65aa | 2026-09-24 | 04b65aa | 5,732 B | A | view · diff |
| git:20260903.b1ad034 | 2026-09-03 | b1ad034 | 5,729 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6403 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
intel/skills · 29 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q522gytpdrwbf2tw GET https://markdownregistry.com/api/v1/resolve?ref=intel/skills/xpu-container-run GET https://markdownregistry.com/api/v1/blob/543b24fcc905dee449e274e3edfca1cc44927ad167b4a76ebd3d11eba2f034f5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.