# A new way to RootFS

**URL:** <https://community.fly.io/t/a-new-way-to-rootfs/19196>\
**Category:** Fresh Produce\
**Created:** [April 10, 2024, 1:43pm UTC](https://community.fly.io/t/a-new-way-to-rootfs/19196 "2024-04-10T13:43:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![JP\_Phillips](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/jp_phillips/32/18337_2.png) [@JP\_Phillips](https://community.fly.io/u/JP_Phillips)\
**Post date:** [April 16, 2024, 7:48pm UTC](https://community.fly.io/t/a-new-way-to-rootfs/19196/2 "2024-04-16T19:48:05Z")

</div>

One thing I failed to highlight in the original post was the implications for anyone creating swapfiles and running `swapon` directly. Originally, machines didn’t have first class support for swap and we had to recommend customers run certain commands as part of the initialization of the machine. Now that it is a first class field in both the [fly.toml](https://fly.io/docs/reference/configuration/#swap_size_mb-option), it will be the only way to configure swap moving forward. Ideally we wouldn’t have to force this change as part of the new rootfs but unfortunately by using overlayfs the `swapon` command fails. If you do configured `swap_size_mb`, we allocate a device to be used for swap.

---

_[View the full topic](https://community.fly.io/t/a-new-way-to-rootfs/19196)._