DOCKER-COMPOSE-KILL(1)

💀 docker-compose-kill — the "bestie it's OVER" button

okay so like. this is docker-compose-kill(1), a page in the Docker Compose manual, and it does exactly what it says on the tin: it force stops service containers. no gentle goodbyes. no "hey are you done?" it's just. done. ✨

---

✨ SYNOPSIS ✨

docker compose kill [OPTIONS] [SERVICE...]

that's it. that's the whole vibe. 🫶

---

🎀 DESCRIPTION 🎀

So basically this command forces running containers to stop by sending a SIGKILL signal. Like, straight to the point. No hand-holding, no asking nicely, no graceful shutdown arc. It just ends them. 💅

But wait, bestie, plot twist — optionally the signal can be passed! So if SIGKILL is giving too much and you want something a little different, you can say so, for example:

$ docker-compose kill -s SIGINT

see? you got range. 🌈

---

🔥 OPTIONS 🔥

• -h, --help[=false] — help for kill. your little "what does this do again" safety net 💖
• --remove-orphans[=false] — Remove containers for services not defined in the Compose file. yes the orphans. someone had to deal with them 🥺
• -s, --signal="SIGKILL" — SIGNAL to send to the container. default is SIGKILL, which is lowkey the most dramatic one, and honestly? iconic 👑

---

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these ones come from the parent command, they're not even kill's own thing, they're just part of the family tree 🌸

• --dry-run[=false] — Execute command in dry run mode. aka you get to rehearse the whole thing without actually doing it. main character energy but with a rehearsal 🎬

---

👑 SEE ALSO 👑

• docker-compose(1) — the mothership. go read her too, fr fr 📖

---

and that's the tea, bestie 🍓 this page is from Docker Compose, dated Mar 2025, and it's the docker-compose-kill(1) entry — so if you ever need to send a container a very firm signal, you know where to find me. slay safe out there 💜🦋

---