docs/composefs: Update with latest - #2298
Merged
Merged
Conversation
jeckersb
enabled auto-merge
July 8, 2026 20:40
jeckersb
added this pull request to the merge queue
Jul 8, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
travier
reviewed
Jul 9, 2026
travier
approved these changes
Jul 9, 2026
travier
left a comment
travier
left a comment
Contributor
There was a problem hiding this comment.
Looking good! One suggestion.
cgwalters
added this pull request to the merge queue
Jul 9, 2026
In particular, this commits us to supporting in-place upgrades from the current state! We will leave things like the EROFS v1 switch as a followon, ensuring that we continue to support that as an upgrade path. Signed-off-by: Colin Walters <walters@verbum.org>
cgwalters
force-pushed
the
composefs-ondisk-stable
branch
from
July 9, 2026 15:20
1808de2 to
2b84179
Compare
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
cgwalters
enabled auto-merge
July 9, 2026 16:48
Collaborator
|
Hm |
auto-merge was automatically disabled
July 9, 2026 17:55
Pull request was closed
jeckersb
enabled auto-merge
July 9, 2026 17:55
jeckersb
added this pull request to the merge queue
Jul 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Jul 9, 2026
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 24, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 25, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 25, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 25, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 26, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 28, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 29, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, --soft-reboot=auto not falling back to a regular reboot, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
cgwalters-bot
added a commit
to cgwalters-forge/bootc
that referenced
this pull request
Sep 30, 2026
We already committed in bootc-dev#2298 to in-place upgrades for every composefs system installed since 1.16.0, the V1/V2 EROFS transition has shipped with its bridge for 1.16 UKIs, and `bootc install mount` (bootc-dev#2483) gives post-install tooling a supported way into a deployment instead of poking at backend paths. What was left was docs and help text calling the backend experimental, which no longer matches what we promise. Stable now, under the same RELEASES.md guarantees as the ostree backend: the backend itself (install, upgrade, switch, rollback, status, usr-overlay, soft reboot, and `bootc install mount`), its on-disk state, BLS installs with GRUB or systemd-boot, UKIs with systemd-boot including sealed ones, fs-verity optional on filesystems without it, the composefs.digest= and bare composefs= kernel arguments, bootc-root-setup.service and setup-root-conf.toml, and the image build commands `bootc container ukify`, `split-kernel-and-rootfs` and `compute-composefs-digest`. The last was hidden only because it belonged to the experimental feature set; it is documented as part of the sealed image flow, so it is now visible and gets a man page. The composefs part of the status JSON (BootEntryComposefs) becomes stable API along with it. Still experimental: the grub-cc bootloader (CI covers it only on Fedora 44, with a GRUB binary side-loaded from ELN), UKI addons (they are only installed at install time, never updated on upgrade, garbage collected or reverted on rollback) and unified storage. compute-composefs-digest-from-storage stays hidden as a debugging aid. Known gaps are listed as limitations rather than as reasons to keep the whole backend experimental: bootc edit, install reset, boot counting, ostree to composefs transitions, --soft-reboot=auto not falling back to a regular reboot, a single ESP without XBOOTLDR, x86_64-only testing, and the upgrade paths that CI actually exercises. The zstd:chunked caveat now names 1.16.12, the first release with the composefs-rs decoder fix. Generated-by: AI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In particular, this commits us to supporting in-place upgrades from the current state!
We will leave things like the EROFS v1 switch as a followon, ensuring that we continue to support that as an upgrade path.