DOCKER(1)

πŸ’– DOCKER(1) πŸ’–

okay bestie, welcome to the Docker User Manuals β€” yes, that's the manual name, and yes, it's giving very "official documentation but make it serve." sit down, grab a boba, and let's talk about yeeting plugins out of your Docker setup 🫢


✨ NAME ✨

docker-plugin-rm β€” Remove one or more plugins πŸ’…

like. the whole job. remove plugin(s). that's the gig. iconic of it honestly.


🌸 SYNOPSIS 🌸

docker plugin rm [OPTIONS] PLUGIN [PLUGIN...]

notice the PLUGIN [PLUGIN...] β€” you can hand it one plugin or a whole lil squad of them, no cap. and [OPTIONS] goes before them, always before them, don't fight the order πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

Remove one or more plugins.

that's it. that's the description. short, sweet, main character energy. you point it at plugin names and they stop existing in your install. periodt πŸ”₯


πŸ’œ OPTIONS πŸ’œ

  • -f, --force[=false] β€” Force the removal of an active plugin. lowkey important: without this, an active plugin is not gonna go quietly. with it? you're telling Docker "bestie I don't care, remove it anyway" πŸ˜­πŸ’€ so only reach for this when you actually mean it.

πŸ‘‘ SEE ALSO πŸ‘‘

docker-plugin(1) β€” the parent page, the whole plugin family, the source of all plugin lore. go read it, iykyk 🌈


that's the whole page, bestie β€” every flag, every arg, nothing skipped, nothing invented. go forth and delete responsibly πŸ’–βœ¨

sending you off with love from the Docker Community, dated Oct 2026 πŸŽ€πŸ¦‹ stay slay, keep your plugins tidy, and remember: --force is a mood, not a personality πŸ’…

πŸ“¦ where this page comes from