runc-run(8)
๐ธ NAME ๐ธ
okay bestie, gather round ๐ runc-run โ create and start a container. that's it, that's the whole vibe. this is the page for runc-run(8) from the System Manager's Manual, and we're gonna read it together, no skimming, i'm watching ๐
โจ SYNOPSIS โจ
runc run [option ...] container-id
that's the whole summoning ritual, bestie ๐ฏ๏ธโจ
๐ฆ DESCRIPTION ๐ฆ
so the run command creates an instance of a container from a bundle, and starts it. simple. iconic. no notes.
and if you wanna think of it in girl-math: run is literally just a shortcut for create and then start back to back ๐ซถ like when you buy the outfit AND the shoes in one checkout. same energy. one command.
๐ OPTIONS ๐
--bundle,-bpath โ the path to the root of the bundle directory. default is the current directory, so if you're already standing in your bundle, you're good ๐--console-socketpath โ the path to anAF_UNIXsocket that's gonna receive a file descriptor pointing at the master end of the console's pseudoterminal. wanna know more? go readdocs/terminalsโจhttps://github.com/opencontainers/runc/blob/master/docs/terminals.mdโฉ ๐--detach,-dโ detach from the container's process. you go your way, it goes its way, no strings ๐ซ--pid-filepath โ tell it which file to write the initial container process' PID to. very "leave a note on the fridge" of you.--no-subreaperโ disables the use of the subreaper that's normally used to reap reparented processes. bye subreaper ๐--no-pivotโ do not use pivot root to jail the process inside the rootfs. like, listen: this should not be used except in exceptional circumstances, and it may be unsafe from the security standpoint โ ๏ธ so don't just casually hit it because you're feeling spicy. this is not the spicy one. this is the danger one. ๐--no-new-keyringโ don't create a new session keyring for the container. consequence: the container will inherit the calling processes session key. lowkey passing down the family keyring ๐ญ--preserve-fdsN โ passNadditional file descriptors into the container. the math isstdio + $LISTEN_FDS + Nin total, and the default is0๐งฎ--keepโ keep the container's state directory and cgroup. this is genuinely helpful if you wanna check the state afterwards, like peeking at cgroup controllers once the container has exited ๐ but heads up: if you use this option, you're gonna need a manualrunc deleteafterwards to clean up an exited container's artefacts. it's the price of keeping receipts, fr fr ๐งพ
๐ SEE ALSO ๐
runc(8). go read the parent page, iykyk ๐
and that's the whole page, bestie!! ๐โจ this was runc-run(8) from the System Manager's Manual โ runc's very own manual, periodt ๐
๐ฆ go create and start something iconic, ily, bye ๐
๐ฆ where this page comes from
- alpine 3.24: runc-doc 1.4.3-r2 ยท Apache-2.0
- arch rolling: runc 1.5.2-1 ยท Apache
- fedora 43: runc 2:1.3.1-1.fc43 ยท Apache-2.0 and BSD-2-Clause and BSD-3-Clause and MIT
- fedora 43: runc 2:1.5.2-3.fc43 ยท Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0
- fedora 44: runc 2:1.4.1-1.fc44 ยท Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0
- fedora 44: runc 2:1.5.2-3.fc44 ยท Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND MPL-2.0
- nixpkgs unstable: runc 1.5.2
- ubuntu resolute: runc 1.4.0-0ubuntu1 ยท Apache-2.0
- ubuntu resolute: runc-stable 1.3.4-0ubuntu1 ยท Apache-2.0
- ubuntu stonking: runc 1.5.1-0ubuntu2 ยท Apache-2.0
- ubuntu stonking: runc-stable 1.5.1-0ubuntu2 ยท Apache-2.0
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms