NVIDIA-CONTAINER-RUNTIME.CDI(1)

👑 NAME 👑

nvidia-container-runtime.cdi — aka nvidia-container-runtime.cdi, bestie. That's the whole name. Short, sweet, iconic. 🎀

---

💖 DESCRIPTION 💖

🌸 NAME: 🌸

okay so first things first: it's runc — the Open Container Initiative runtime. periodt. 💅

runc is a command line client for running applications packaged according to the Open Container Initiative (OCI) format, and it's a compliant implementation of the Open Container Initiative specification. no cap, it literally follows the spec. ✨

runc integrates well with existing process supervisors to provide a production container runtime environment for applications. so like, it plays nice with your existing process monitoring tools, and the container gets spawned as a direct child of the process supervisor. it's giving teamwork. 🫶

Containers are configured using bundles. A bundle for a container is a directory that includes a specification file named config.json and a root filesystem. The root filesystem contains the contents of the container. (yes bestie, the bundle is just a folder with a config.json and a rootfs in it. that's the whole vibe.) 🌈

To start a new instance of a container:

# runc run [ -b bundle ] <container-id>

Where "<container-id>" is your name for the instance of the container that you are starting. The name you provide for the container instance must be unique on your host — like, no duplicate names, that's not the move. 🙈 Providing the bundle directory using -b is optional. The default value for "bundle" is the current directory. so if you're already standing in the bundle, you don't even gotta say anything. slay. 💅

---

🧚 USAGE: 🧚

runc [global options] command [command options] [arguments...]

---

⭐ VERSION: ⭐

1.5.1-0ubuntu2

---

🎀 COMMANDS: 🎀

• checkpoint — checkpoint a running container
• create — create a container
• delete — delete any resources held by the container often used with detached container
• events — display container events such as OOM notifications, cpu, memory, and IO usage statistics
• exec — execute new process inside the container
• kill — kill sends the specified signal (default: SIGTERM) to the container's init process
• list — lists containers started by runc with the given root
• pause — pause suspends all processes inside the container
• ps — ps displays the processes running inside a container
• restore — restore a container from a previous checkpoint
• resume — resumes all processes that have been previously paused
• run — create and run a container
• spec — create a new specification file
• start — executes the user defined process in a created container
• state — output the state of a container
• update — update container resource constraints
• features — show the enabled features
• help, h — Shows a list of commands or help for one command

---

💜 GLOBAL OPTIONS: 💜

• --debug — enable debug logging
• --log value — set the log file to write runc logs to (default is '/dev/stderr')
• --log-format value — set the log format ('text' (default), or 'json') (default: "text")
• --root value — root directory for storage of container state (this should be located in tmpfs) (default: "/run/runc")
• --systemd-cgroup — enable systemd cgroup support, expects cgroupsPath to be of form "slice:prefix:name" for e.g. "system.slice:runc:434234"
• --rootless value — ignore cgroup permission errors ('true', 'false', or 'auto') (default: "auto")
• --help, -h — show help
• --version, -v — print the version

---

🦋 SEE ALSO 🦋

The full documentation for nvidia-container-runtime.cdi is maintained as a Texinfo manual. If the info and nvidia-container-runtime.cdi programs are properly installed at your site, the command

info nvidia-container-runtime.cdi

should give you access to the complete manual. go read it bestie, it's right there 🍓

---

ok that's the whole page, no notes. nvidia-container-runtime.cdi 1…. June 2026 — NVIDIA-CONTAINER-RUNTIME.CDI(1). mwah 💋 stay containerized, queen 👑