autopkgtest-schroot(1)

💖 autopkgtest-schroot(1) — the Linux Programmer's Manual glow-up 💖

okay bestie, sit down, hydrate, because this is the autopkgtest-schroot(1) page and she is serving schroot-based virtualisation 🦋

---

✨ NAME ✨

autopkgtest-schroot — an autopkgtest virtualisation server that uses a schroot, no cap 💅

---

🌸 SYNOPSIS 🌸

autopkgtest [...] -- schroot [options] schroot-name

---

🎀 DESCRIPTION 🎀

So like, autopkgtest-schroot gives you an autopkgtest virtualisation server built on top of a schroot. Most of the time you're not even calling her directly — autopkgtest invokes her for you. She's the backstage crew, the main character energy happens elsewhere 💖

You must tell her which schroot name to use. That part is not optional, she's not guessing for you 🙈

⚠️ Only use this with schroots that provide temporary sessions — meaning type=file or type=directory with a configured union-type. If you hand her a static "directory" type schroot, autopkgtest-schroot will literally refuse to work. She said no 💀

Also, real talk: schroot does not provide significant isolation between the testbed and the host system. So if the packages you're testing are untrusted, please please please use a different virtualisation server. Not worth the risk, babe 😭

Oh and if you want to make schroots conveniently, mk-sbuild(1) is right there for you, she's iconic 👑

---

🔐 PERMISSIONS 🔐

If you can access the schroot as your own user — like, according to the schroot's users/groups configuration — then you should run autopkgtest-schroot (and autopkgtest itself) as a normal user too. No need to escalate for no reason, bestie ✨

autopkgtest-schroot reads the schroot configuration (root-users/root-groups) to figure out whether she can enter the schroot as the root user. If she can, she sets the root-on-testbed capability and suddenly you can run tests that need to build or run as root. Slay 🫶

But if your user isn't allowed to do that? Then you need to run autopkgtest as root instead. That's just the vibe check she's giving you 🌈

---

💅 OPTIONS 💅

• -s ID | --session-id=ID — use a custom schroot session ID. This one's a gift because it lets you easily spot hung sessions in schroot --list --all-sessions. So thoughtful of her 🎀
• -d | --debug — turns on debugging output. When things are weird, this is your bestie fr fr 🔥

---

📥 INPUT, OUTPUT AND EXIT STATUS 📥

The behaviour of autopkgtest-schroot is exactly as described by the AutomatedTesting virtualisation regime specification. That's the whole vibe, go read the spec, iykyk 💜

---

👀 SEE ALSO 👀

• autopkgtest(1)
• autopkgtest-virt-null(1)
• schroot(1)
• mk-sbuild(1)

---

👑 AUTHORS AND COPYRIGHT 👑

This manpage is part of autopkgtest, a tool for testing Debian binary packages. autopkgtest is Copyright (C) 2006-2013 Canonical Ltd and others. Respect the elders 💖

See /usr/share/doc/autopkgtest/CREDITS for the list of contributors and the full copying conditions. Receipts are all there, bestie 🧚

---

and that's the whole page, you ate it up ⭐ this came to you from the autopkgtest manual, dated 2013, and yeah she's still cute. mwah 💋