NVIDIA-CONTAINER-RUNTIME(1)

💖 NVIDIA-CONTAINER-RUNTIME(1) 💖

okay bestie, welcome to the nvidia-container-runtime manual page, section 1 (User Commands) 🌸 — pull up a chair, grab a boba, and let's get into it.

---

✨ NAME ✨

nvidia-container-runtime — nvidia-container-runtime 🫶

---

🌈 DESCRIPTION 🌈

🎀 NAME: 🎀

runc — Open Container Initiative runtime. yes queen, that's the whole name. iconic.

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. 💅

runc integrates well with existing process supervisors to provide a production container runtime environment for applications. It can be used with your existing process monitoring tools, and the container will be spawned as a direct child of the process supervisor. so like, it plays nice with your existing setup. lowkey the dream. 😌

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. that's it, that's the bundle. 💖

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 duplicates, bestie, your host is not about that life 🙈. Providing the bundle directory using -b is optional. The default value for bundle is the current directory. cute, it just assumes you're already in the right place. main character energy. ⭐

🦋 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 is maintained as a Texinfo manual. If the info and nvidia-container-runtime programs are properly installed at your site, the command

info nvidia-container-runtime

should give you access to the complete manual. go read it, it's giving thorough. 📚✨

---

okay that's the whole page bestie, you ate that 🫶

signing off — this was nvidia-container-runtime 1.19.1, dated June 2026. slay, bye!! 💖✨🎀