NVIDIA-CONTA...UNTIME.LEGACY(1)

💖 NAME 💖

nvidia-container-runtime.legacy — bestie, that's literally the whole name, it's giving "the title is the title" ✨

---

🌸 DESCRIPTION 🌸

👑 NAME:

runc — the Open Container Initiative runtime, no cap 💅

runc is a command line client for running applications packaged according to the Open Container Initiative (OCI) format, and it's a fully compliant implementation of the Open Container Initiative specification. Periodt. 🫶

runc integrates so well with the process supervisors you already have running — it's lowkey the moment where you get a production container runtime environment for your apps. You can pair it with your existing process monitoring tools, and the container just gets spawned as a direct child of the process supervisor. Iconic behaviour, honestly. 🌈

Containers get 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 holds the contents of the container. 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 you're starting. Heads up bestie: the name you give the container instance must be unique on your host, no duplicates allowed, the vibe check is strict 💀. Providing the bundle directory with -b is optional, and the default value for bundle is the current directory. Easy. 🌸

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

info nvidia-container-runtime.legacy

should give you access to the complete manual. Go get your lore, bestie 📚💖

---

okay that's the whole page, mwah 💋 — this was nvidia-container-runtime.legacy…, dated June 2026, and the manual is NVIDIA-CONTA...UNTIME.LEGACY(1). slay, you read the whole thing, I'm so proud of you 🥹👑