The Fedora Linux 40 Beta was released today[1] and our Fedora CoreOS next stream has been migrated to Fedora Linux 40 content. Existing nodes on the next stream will update as normal over the following days.
The Fedora Project accepted changes for Fedora 40 are in the Wiki[2] and the Fedora CoreOS analysis of each change is documented in the tracker[3].
The following changes require special attention:
- Podman v5.0
The following changes may impact some specific setups:
- Switch to using OSBuild for most CoreOS boot image building
- Newly deployed
qemuor baremetalsystems will use disk images built using OSBuild. - Switch to using OSBuild for most CoreOS boot image building · Issue #1653 · coreos/fedora-coreos-tracker · GitHub
- Newly deployed
- Enable IPv4 Address Conflict Detection by default
- Conflict detection can delay startup by ~200ms.
- Changes/Enable IPv4 Address Conflict Detection - Fedora Project Wiki
- Fedora 40 Changes: Enable IPv4 Address Conflict Detection by default · Issue #1656 · coreos/fedora-coreos-tracker · GitHub
- Assign individual, stable MAC addresses for Wi-Fi connections
- If you are using WiFi, then your systems MAC address will likely change after the update.
- Changes/StableSSIDMACAddress - Fedora Project Wiki
- Switch pam_userdb from BerkeleyDB to GDBM
- If you have overlayed vsftpd on your systems and use pam_userdb, then you need to convert the database using the instructions from pam_userdb.
- Changes/PamBerkeleyDBtoGdbm - Fedora Project Wiki
- Fedora 40 Change: Switch pam_userdb from BerkeleyDB to GDBM · Issue #1634 · coreos/fedora-coreos-tracker · GitHub
Please test out the next stream over the coming weeks and report any issues in our issue tracker[4].
Thank you to everyone helping find issues by running the next stream!
The Fedora CoreOS Team