News › linux
By The Linux Camp News, November 4, 2026
Fedora 45 adds Stratis installation paths and browser-based installation for Atomic Desktops. Silverblue and Kinoite gain preview disk images, while removed Podman backends warrant configuration checks.
Fedora Linux 45 was released on November 3, 2026, covering Workstation, KDE Plasma Desktop, Server, Cloud, CoreOS and IoT, alongside Atomic Desktops and Spins. For deployment workflows, two notable changes are support for installing onto Stratis storage and the adoption of Anaconda WebUI by Atomic Desktop installer images. 3 1 2
The Stratis addition connects storage selection to both automated and interactive installation. Kickstart, Fedora's automated installation route, gains Stratis support; manual partitioning uses Cockpit Storage within Anaconda WebUI. That gives deployment teams two ways to specify a Stratis installation target. The documented change adds an option rather than announcing Stratis as the default filesystem. 4 1
For Atomic Desktop installations, the WebUI also enables an operator to use a browser on another machine over HTTPS. This extends an existing Fedora installer transition: Workstation adopted the interface in Fedora 42, followed by Spins in Fedora 43. The release report establishes remote installation support, but does not specify authentication, certificate handling or startup requirements, so it is not a complete remote-deployment procedure. 2
Atomic Desktop ISO production also moves to Image Builder. The release report expects no immediate visible ISO changes, but says the build path enables pre-installed disk images and prepares for a future move to bootable container images. As documented in the report retrieved November 4, those disk images remain previews limited to Silverblue and Kinoite because only those variants have the required first-boot experience. 2
Before moving container workflows to Fedora 45, check whether their Podman configurations depend on slirp4netns or the BoltDB backend. The Atomic Desktop release report explicitly lists both as removed, making dependency review more useful than assuming existing configurations will remain supported. It provides no replacement configuration or migration procedure; those steps need separate verification. 2