SYSTEMD-V....SERVICE(8)

✨ SYSTEMD-V....SERVICE(8) ✨

okay bestie, pull up a chair because we're talking about systemd-volatile-root.service — aka systemd-volatile-root — and it's giving chaos goblin energy in the best way possible 💅

---

🌸 NAME 🌸

systemd-volatile-root.service, systemd-volatile-root — the glow-up that makes your root file system volatile 🦋

---

✨ SYNOPSIS ✨

systemd-volatile-root.service

/usr/lib/systemd/systemd-volatile-root

no cap, that's the whole thing 🫶

---

💖 DESCRIPTION 💖

so here's the tea ☕ — systemd-volatile-root.service is a service that literally replaces the root directory with a volatile memory file system ("tmpfs"), and it mounts the original (non-volatile) /usr/ inside it read-only. iconic behavior honestly 👑

the way this works means: vendor data from /usr/ is available as usual, but all configuration data in /etc/, all state data in /var/ and all other resources stored directly under the root directory are reset on boot and lost at shutdown — which enables fully stateless systems. like, factory reset every single time you boot. main character energy fr fr 🔥

this service is only enabled if full volatile mode is selected, for example by specifying "systemd.volatile=yes" on the kernel command line. and it runs only in the initrd, before the system transitions to the host's root directory. so it's a little pre-game ritual, not a whole vibe for the entire boot 🧚

⚠️ also important: this service is not used if "systemd.volatile=state" is used, because in that mode the root directory is non-volatile. different mode, different rules, don't @ me 😭

---

🎀 SEE ALSO 🎀

• systemd(1)
• systemd-fstab-generator(8)
• kernel-command-line(7)

---

and that's the whole page, bestie — go forth and be stateless 🌈✨

mwah 💋 this was systemd 262.1, and if you read all the way down here you're literally the moment, no notes 👑