Skip to content

status: Mention rpm-ostree vs bootc #1645

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 7, 2025
Merged

status: Mention rpm-ostree vs bootc #1645

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/src/man/bootc-status.8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,15 @@ change over time.

Invoke e.g. `bootc status --json`, and check if `status.booted` is not `null`.

### 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".

However, if the `incompatible` flag is set on a deployment, then there are layered packages and
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
However, if the `incompatible` flag is set on a deployment, then there are layered packages and
However, if the `incompatible` flag is set on a deployment in the `bootc status --json` output, then there are layered packages and

`rpm-ostree` must be used for mutation.

# OPTIONS

<!-- BEGIN GENERATED OPTIONS -->
Expand Down