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, 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.
2 Likes