podman-quadlet-rm(1)

πŸ“¦
version 6.1.4 Β· 3 versions
, in arch rolling

πŸ’… podman-quadlet-rm(1) β€” the girlies' guide to yeeting quadlets

Okay so bestie, welcome to podman-quadlet-rm(1) from the General Commands Manual β€” this is the page where we learn how to remove an installed quadlet. Slay. Let's get into it πŸŽ€


✨ NAME ✨

podman-quadlet-rm β€” Removes an installed quadlet πŸ’«


πŸ¦‹ SYNOPSIS πŸ¦‹

podman quadlet rm [options] quadlet|application [quadlet|application]...

🌸 DESCRIPTION 🌸

So what this does, bestie: it removes one or more installed Quadlets from the current user. Iconic. And it's not picky β€” the command also takes an application name as input, and it removes all the Quadlets that belong to that specific application. One name, whole app gone, no notes πŸ’…

Now here's the part where you gotta pay attention πŸ™ˆ When the argument you pass is an uninstantiated template quadlet, this command removes the template quadlet file (e.g. templateName@.container) and the generated systemd template unit (e.g. templateName@.service). If there are running instances of that systemd template, the command fails if the --force option is not set β€” and if --force is set, it tries to stop the instances. So like, --force is the main character here, fr fr.

🫢 Note: If a quadlet is part of an application, removing that specific quadlet will remove the entire application. And when a quadlet is installed from a directory, all files installed from that directory β€” including both quadlet and non-quadlet files β€” are considered part of a single application. So yeah, it's giving "one of us is all of us." Be careful, bestie. 😭

⭐ OPTIONS ⭐

  • --all, -a β€” Remove all Quadlets for the current user. Every single one. Clean sweep, no crumbs. 🧚
  • --force, -f β€” Remove running Quadlets. In the case of uninstantiated template quadlets, this stops its instances. πŸ’€
  • --ignore, -i β€” Do not error for Quadlets that do not exist. Basically, if it's not there, we're not gonna make it a whole thing. πŸ™ˆ
  • --recursive β€” Required when removing applications (default false). Yes, required β€” so don't skip it and then be confused. πŸ”₯
  • --reload-systemd β€” Reload systemd after the operation completes (default true). In order to disable it, users need to manually set the value of this flag to false. So you have to go out of your way to turn it off, iykyk. ⭐

🌈 EXAMPLES 🌈

Removing a single quadlet, easy peasy:

$ podman quadlet rm myquadlet.container
myquadlet.container

And here's the --recursive moment for when you're nuking a whole app (note the required flag, bestie πŸ‘‘):

$ podman quadlet rm --recursive myapp
web.container
data.container
data.volume

Look at that output. Ate. πŸ’…


πŸ’œ SEE ALSO πŸ’œ

podman(1), podman-quadlet(1), podman-systemd.unit(5)


That's the whole page, bestie β€” you now officially understand quadlet removal, periodt ✨ Go forth and clean up responsibly 🫢

Signing off from the General Commands Manual, this was podman-quadlet-rm(1) β€” podman-quadlet-rm(1), version vibes only, no date on the tin but the footer said so πŸŽ€πŸŒΈ

πŸ“¦ where this page comes from