DEBSPAWN-LOGIN(1)
β¨ DEBSPAWN-LOGIN β¨
okay bestie, so this is the manual page for debspawn login β the lil' command from Debspawn that yeets you straight into a container and hands you a shell π«Ά it's filed under section 1, and it's giving "let me in, let me iiiin" energy. π
πΈ NAME πΈ
debspawn-login β open an interactive shell session in a container πβ¨
π SYNOPSIS π
debspawn login [-h|--help] [--variant] [-a|--arch] [--suite]
[--persistent] [--allow] [--boot] {NAME}
likeβ¦ look at her. all those flags lined up like a fit check. π
π DESCRIPTION π
so basically this command drops you into an interactive shell session inside a container β and not just any container, specifically one that's normally used for building π¨
why would you even want that, you ask? because:
- you can inspect the build environment and see what's actually going on in there π
- you can manually customize the container image for special applications β but ONLY if the
--persistentflag is set, otherwise your changes ghost you π
periodt. that's the whole vibe.
β¨ OPTIONS β¨
NAMEβ the name of the container image (usually it's just a distribution suite name, iykyk). this one's the main character, she's required. π-h,--helpβ prints a brief lil' help thing about all the available commands. your "wait what was that flag again" bestie π«Ά--variantβ sets the variant of the selected image, the one that was used for bootstrapping. lowkey important, don't skip her. π-a,--archβ the architecture of the base image that should be selected. pick your fighter π₯--suiteβ explicitly set a suite name, instead of letting it be derived from the container name. sometimes you just gotta spell it out for them π--persistentβ makes changes done in the session persistent π₯ this is THE one to remember: no--persistent, no saved changes. that's it, that's the deal.--allowβ list one or more additional permissions to grant the container. takes a comma-separated list of capability names. yes, commas. no spaces needed, she's low-maintenance. β¨--bootβ boot the container image (this requires the image to actually contain an init system, so no init = no boot, sorry babe π).
π¦ SEE ALSO π¦
debspawn(1), systemd-nspawn(1). go read those too, they're the supporting cast and they ate π
π AUTHOR π
this manual page was written by Matthias Klumpp <mak@debian.org>. thank you for your service, king π«‘β¨
π COPYRIGHT π
Copyright Β© 2018-2022 Matthias Klumpp
and that's the whole page, bestie!! ππ this was the debspawn login manpage from Debspawn, filed in section 1 of the manual β no version number on the tin, just the source name and the vibe. now go forth and inspect those build environments, you gorgeous little sysadmin π¦π
β¨
π¦ where this page comes from
- debian bookworm: debspawn 0.6.2-1 Β· LGPL-3.0-or-later
- debian trixie: debspawn 0.6.4-2 Β· LGPL-3.0-or-later
- ubuntu noble: debspawn 0.6.4-1 Β· LGPL-3.0-or-later
- ubuntu resolute: debspawn 0.6.4-2 Β· LGPL-3.0-or-later
- ubuntu stonking: debspawn 0.6.5-1 Β· LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms