DOCKER-BUILDX-RM(1)

💖 DOCKER-BUILDX-RM 💖

okay bestie, welcome to docker-buildx-rm(1) — the page where we learn how to yeet builder instances into the void 🗑️✨

---

🌸 NAME 🌸

docker-buildx-rm — remove one or more builder instances. plural. we're not just deleting one thing, we're deleting things. 👑

---

✨ SYNOPSIS ✨

docker buildx rm [OPTIONS] [NAME] [NAME...]

---

🦋 DESCRIPTION 🦋

So basically? It removes the builder you named. Or, if you didn't name anyone, it removes the current one. main character energy but make it destructive 💅

⚠️ And here's the lil plot twist: if you try to remove the default builder, it's a no-op. Like, nothing happens. It's giving "the door is locked and honestly that's for your own good." 🚪🔒

---

🎀 OPTIONS 🎀

• --all-inactive[=false] — remove all the inactive builders. not one. not two. all of them. go off 😤
• -f, --force[=false] — do not prompt for confirmation. no lil "are you sure?" moment, we just go 🚀
• -h, --help[=false] — help for rm. the classic. the icon. the "wait what does this do again" savior 🫶
• --keep-daemon[=false] — keep the BuildKit daemon running. we're breaking up with the context, not the daemon. respectful. mature. 💜
• --keep-state[=false] — keep BuildKit state, so a new builder with the same name can reuse it later. it's not goodbye, it's "see you around" 😭

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

• --builder="" — override the configured builder instance. your builder, your rules ✨

---

🔥 EXAMPLE 🔥

### Remove all inactive builders (--all-inactive) {#all-inactive}

Remove builders that are not in running state. bye to everyone who isn't thriving rn 🙈

$ docker buildx rm --all-inactive
WARNING! This will remove all builders that are not in running state. Are you sure you want to continue? [y/N] y

---

Override the configured builder instance (--builder) {#builder}

Same as ⟨/reference/cli/docker/buildx/#builder⟩. literally the same thing bestie, go read that one 🧚

---

Do not prompt for confirmation (--force) {#force}

Do not prompt for confirmation before removing inactive builders. no questions, no hesitation, no "u sure?" — periodt 💅

$ docker buildx rm --all-inactive --force

---

Keep the BuildKit daemon running (--keep-daemon) {#keep-daemon}

Keep the BuildKit daemon running after the buildx context is removed. This is useful when you manage BuildKit daemons and buildx contexts independently. 🔧

🚨 but listen — this is Only supported by the ⟨/build/drivers/docker-container/⟩ and ⟨/build/drivers/kubernetes/⟩ drivers. so if you're on anything else, this is not the vibe.

---

Keep BuildKit state (--keep-state) {#keep-state}

Keep BuildKit state, so it can be reused by a new builder with the same name. ♻️

🚨 Currently, only supported by the ⟨/build/drivers/docker-container/⟩.

---

👑 SEE ALSO 👑

docker-buildx(1) — go read the parent, it raised this one 🌱

---

that's the whole page bestie, hope your builders rest in peace 🕊️

this was DOCKER-BUILDX-RM(1), from Apr 2025 — mwah, stan, slay, bye 💖✨🎀