BOOTC-STATUS(8)

💖 BOOTC-STATUS(8) 💖

okay bestie, welcome to bootc-status from the System Manager's Manual, section 8 (that's the "sysadmin, we live here now" section, iykyk 🫶). This is the little command that tells you what's actually going on with your system. Let's get into it. ✨

---

🌸 NAME 🌸

bootc-status — Display status. that's it. that's the whole job. and she does it flawlessly 💅

---

🎀 SYNOPSIS 🎀

bootc status [OPTIONS...]

---

🦋 DESCRIPTION 🦋

Display status. 💫

So here's the tea: if standard output is a terminal, this outputs a description of the bootc system state — like, a nice readable lil vibe check for your eyeballs. But if standard output is not a terminal (aka you're piping it somewhere, bestie), it outputs a YAML-formatted object using a schema intended to match a Kubernetes resource that describes the state of the booted system. iconic behavior honestly 👑

So basically: same command, two completely different fits depending on where the output is going. main character energy that adapts to the room. 🌈

🧚 Parsing output via programs

Either the default YAML format or --format=json can be used.

⚠️ Do not attempt to explicitly parse the output of --format=humanreadable — it will very likely change over time. fr fr, do not do this. it's giving fragile. 💀

🔍 Programmatically detecting whether the system is deployed via bootc

Invoke e.g. bootc status --json, and check if status.booted is not null. simple as that, bestie ✨

💜 Detecting rpm-ostree vs bootc

There is no "bootc runtime". When used with the default ostree backend, bootc and tools like rpm-ostree end up sharing the same code and doing effectively the same thing. Hence, there isn't a mechanism to detect if a system "is bootc" or "is rpm-ostree".

like... they ARE each other. it's the same code underneath. they're sharing a brain cell and honestly? slay. 🧠✨

However, if the incompatible flag is set on a deployment, then there are layered packages and rpm-ostree must be used for mutation. no cap. 👑

---

✨ OPTIONS ✨

• --format=FORMAT — The output format 💅 Possible values:
  • humanreadable
  • yaml
  • json
• --format-version=FORMAT_VERSION — The desired format version. There is currently one supported version, which is exposed as both 0 and 1. Pass this option to explicitly request it; it is possible that another future version 2 or newer will be supported in the future 🌟
• --booted — Only display status for the booted deployment. just the one we're running on rn, bestie 🥾
• -v, --verbose — Include additional fields in human readable format 🔍✨

---

🔥 EXAMPLES 🔥

Show current system status:

bootc status

Show status in JSON format:

bootc status --format=json

Show detailed status with verbose output:

bootc status --verbose

Show only booted deployment status:

bootc status --booted

---

👑 SEE ALSO 👑

bootc(8), bootc-upgrade(8), bootc-switch(8), bootc-rollback(8)

go read those too, bestie, they're all part of the same lil family 🫶🌺

---

🌈 VERSION 🌈

v1.17.1

---

okay that's the whole page! 💖 this was BOOTC-STATUS(8) from the System Manager's Manual, and we're sitting pretty at version v1.17.1. thank you for coming to my ted talk, go check your status, and remember: pipe it to YAML if you're scripting, never parse the humanreadable one, and always know whether you're booted. mwah! 🎀💅🌸✨