DOCKER(1)

πŸ’… DOCKER-PLUGIN-UPGRADE β€” like, the glow-up era for your plugins ✨

okay bestie, welcome to the Docker User Manuals section for DOCKER(1) 🫢 this one's short and sweet and honestly? it ate.


🌸 NAME 🌸

docker-plugin-upgrade β€” upgrade an existing plugin πŸ’–

that's it. that's the whole job. she takes an old plugin and makes her new again. main character energy fr fr.


✨ SYNOPSIS ✨

docker plugin upgrade [OPTIONS] PLUGIN [REMOTE]

look at her. so clean. so simple. so iconic. πŸ‘‘


πŸ¦‹ DESCRIPTION πŸ¦‹

Upgrade an existing plugin.

no cap, that's literally what it does. you point it at a plugin, and it upgrades her. it's giving "glow-up montage in a teen movie" but for container plugins. πŸ’…


πŸŽ€ OPTIONS πŸŽ€

  • --grant-all-permissions[=false] β€” Grant all permissions necessary to run the plugin. yes queen, hand over the keys πŸ”‘ this one says "you have my blessing, take every permission you need." defaults to false, so if you want it you gotta ask for it out loud, bestie.
  • --skip-remote-check[=false] β€” Do not check if specified remote plugin matches existing plugin image. basically: "don't vibe check the remote, just go" πŸ™ˆ defaults to false, meaning by default she <em>does</em> check the remote against the existing plugin image. set it and she skips that whole conversation.
⚠️ heads up: these both default to false, so the chillest, most cautious behaviour is what you get unless you explicitly opt in. iykyk πŸ’–

🌈 SEE ALSO 🌈

  • docker-plugin(1) β€” the whole plugin family, go say hi to the rest of the squad 🫢

and that's the whole page!! short king of a manpage, honestly. periodt πŸ’€βœ¨

🌸 this lil love letter to the docs came from the Docker Community, dated Oct 2026 β€” mwah, tysm for reading bestie, go upgrade something gorgeous πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from