DEBSPAWN-UPDATE(1)

πŸ“¦
version 0.6.5 Β· 2 versions
  • 0.6.5 Β· debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking (latest)
  • 0.5.2 Β· ubuntu jammy
, in debian bookworm, debian trixie, ubuntu noble, ubuntu resolute, ubuntu stonking

🌸 DEBSPAWN-UPDATE(1) β€” the debspawn update glow-up guide 🌸

okay so bestie, welcome to debspawn-update, aka section 1 of the debspawn manual. this is the page about giving your container images a lil refresh. sit down, grab a snack πŸ“, we're doing this.


✨ NAME ✨

debspawn-update β€” Update a container image πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

debspawn update [-h|--help] [--variant] [-a|--arch] [--suite]
                [--recreate] {NAME}

like, that's the whole vibe. update subcommand, then some optional lil flags, then the name. no cap.


πŸ’– DESCRIPTION πŸ’–

so what does debspawn update actually do? it updates a container base image. and honestly? it's the same thing as running apt update && apt full-upgrade on that base image and then making all those changes permanent. the way it just... commits to the bit. iconic.

but wait, there's more (there's always more). debspawn update will also prune all the caches and make sure every required package and script is installed in the container image. so it's not just updating, it's doing a full little self-care routine πŸ§–β™€οΈβœ¨

here's the tea though, and this is the useful part: if you run debspawn update on the images that are in use about once a week, your builds will happen faster. why? because there'll be fewer changes that have to be done before each build. less work later = faster builds later. it's giving investing in your future self. 🫢


🌈 EXAMPLES 🌈

updating images is genuinely so easy, bestie. you just pass the same arguments you used when you created them β€” but you use the update subcommand instead of whatever you used before. that's it. that's the trick. iykyk.

$ debspawn update sid
$ debspawn update --arch=i386 cosmic

look at that. two lines. slayed. πŸ‘‘


πŸ’… OPTIONS πŸ’…

okay here's the part where we go through every single flag, because we don't skip. periodt.

  • NAME β€” the name of the container image. usually it's just a distribution suite name, so like, sid or whatever suite you're on. it's the one required thing here, so don't forget it. πŸ™ˆ
  • -h|--help β€” prints brief help information about the available commands. it's the "bestie i'm lost" button. use it freely, no shame.
  • --variant β€” sets the variant of the selected image, the one that was used for bootstrapping. so if you bootstrapped with a specific variant, this is where you say so.
  • -a|--arch β€” the architecture of the base image that should be selected. i386? arm64? whatever your heart desires, that's what goes here.
  • --suite β€” explicitly set a suite name. this one's for when you want to say the suite out loud instead of having it derived from the container name. main character energy: you decide, not the container. ✨
  • --recreate β€” re-create the container image from scratch using the settings that were used to create it previously, instead of just updating it. so like... it's not a glow-up, it's a whole rebirth. πŸ”₯ same settings as before, brand new image. dramatic? yes. useful? also yes.

πŸŽ€ SEE ALSO πŸŽ€

debspawn-create(1), debspawn-build(1).

go read those too, bestie, they're the friend group. 🫢


πŸ‘‘ AUTHOR πŸ‘‘

this manual page was written by Matthias Klumpp <mak@debian.org>. thank you for your service. 🫑


Copyright Β© 2018-2022 Matthias Klumpp


and that's the whole page, no crumbs left. every flag accounted for, every fact intact, zero skipped sections. we ate. 🍽️✨

okay bye bestie, this was the Debspawn manual's debspawn-update(1) page, section 1, straight from the source β€” no date on this footer, it's just vibing with the source name like that. now go update your images weekly and make your builds faster. mwah. πŸ’‹πŸ’–

πŸ“¦ where this page comes from