# ComposeFS information for F42 upgrades

**URL:** <https://universal-blue.discourse.group/t/composefs-information-for-f42-upgrades/7995>\
**Category:** Bluefin\
**Tags:** announcements, bluefin-news\
**Created:** [April 21, 2025, 9:00pm UTC](https://universal-blue.discourse.group/t/composefs-information-for-f42-upgrades/7995 "2025-04-21T21:00:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![j0rge](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/j0rge/32/8_2.png) [@j0rge](https://universal-blue.discourse.group/u/j0rge)\
**Post date:** [April 21, 2025, 9:00pm UTC](https://universal-blue.discourse.group/t/composefs-information-for-f42-upgrades/7995/1 "2025-04-21T21:00:41Z")

</div>

Hello everyone! I’ll have more details in when the F42 announcement but wanted to give you a heads up now so you can prepare if need be. Due to the adoption of composefs by default in Fedora 42 that upgrade is likely a **one way trip.**

That means once you upgrade to `stable` when it is released that you will **NOT** be able to rebase back to `gts`. However you can disable `composefs`, we do not recommend this unless you upgraded and found a critical problem and need to go back:

```
sudo rpm-ostree kargs --append='ostree.prepare-root.composefs=0'

```

Refer to the upstream documentation for more information: [Composefs :: Fedora Docs](https://docs.fedoraproject.org/en-US/fedora-coreos/composefs/#_disable_composefs)

We’ll update the documentation with more warnings about rebasing, and we will be updating the rebase helper to ensure that you don’t put yourself in that situation. This means that casual rebasing isn’t going to be a thing this cycle, but once the cutover is complete in the fall we’ll reinvestigate.

## How we played ourselves.

In our own small way we helped make this happen.

It’s an example on how a [donation of an open source project](https://universal-blue.discourse.group/t/red-hat-is-donating-bootc-podman-composefs-and-others-to-the-cncf/5112) can really accelerate stuff. We’re not special in that regard, this is what usually happens when cool stuff goes into the CNCF. We were just at the right place at the right time picking the right tech. 😄

Composefs is going to be everywhere (inside flatpaks too), and we have to get this transition done now and as quickly as possible.

Would composefs probably ended up everywhere anyway? Yeah probably, but at least you know it’s got a long term plan attached to it.

- [GitHub - composefs/composefs: The reliability of disk images, the flexibility of files](https://github.com/composefs/composefs)

---

<div class="post-metadata">

**Author:** ![fenglengshun](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/fenglengshun/32/367_2.png) [@fenglengshun](https://universal-blue.discourse.group/u/fenglengshun)\
**Post date:** [April 22, 2025, 3:49am UTC](https://universal-blue.discourse.group/t/composefs-information-for-f42-upgrades/7995/2 "2025-04-22T03:49:20Z")

</div>

Honestly, will all the stuff happening around composefs (nix, `/` device showing up, can’t rebase down) it would have been handy to have this thread months ago.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/univeral_blue/original/2X/e/e39f7d1952979cf23b0f8d634e025fb38da50026.png) [@system](https://universal-blue.discourse.group/u/system)\
**Post date:** [July 21, 2025, 3:50am UTC](https://universal-blue.discourse.group/t/composefs-information-for-f42-upgrades/7995/3 "2025-07-21T03:50:10Z")

</div>

Closed on July 21, 2025, 3:50am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.