runc-kill(8)

πŸ’… runc-kill β€” the manual page, but make it a group chat

okay bestie, welcome to runc-kill, part of the System Manager's Manual squad. this is the lil command that yells at your container. literally. it sends a signal to it. that's the whole job. and it eats. πŸŽ€


✨ NAME ✨

runc-kill β€” send a specified signal to container 🫢


✨ SYNOPSIS ✨

runc kill container-id [signal]

yes that's it. that's the whole vibe check. container-id is required, signal is optional because we're generous like that. 🌸


✨ DESCRIPTION ✨

so, by default, runc kill sends SIGTERM to the container's initial process only. just the one. the main character. not the whole friend group. πŸ‘‘

not me assuming it nukes everything β€” it does NOT. initial process only, bestie. no cap.

if you wanna send a different signal, you've got options (iconic of you):

  • by its name β€” with or without the SIG prefix, both slay ✨
  • by its numeric value β€” for when you're feeling mysterious πŸ’€

and if you're sitting there like "what signals even exist tho" β€” use kill(1) with the -l option to list all the available ones. go look. it's giving reference material. πŸ“‹


✨ EXAMPLES ✨

the following will send a KILL signal to the init process of the ubuntu01 container:

# runc kill ubuntu01 KILL

see how clean that is?? container id, then the signal name, no SIG needed, no notes. ate. πŸ”₯


✨ SEE ALSO ✨

  • runc(1) β€” the whole runc cinematic universe, go read it πŸ¦‹

and that's the page!! mwah πŸ’–

cute lil sign-off: this was runc-kill(8), hanging out in the System Manager's Manual section, brought to you by the runc girlies. go signal something responsibly, bestie. periodt. 🌈⭐

πŸ“¦ where this page comes from