AlmaLinux is taking firm steps to refine its user and administration experience, following releases such as Alma Linux 9.6and the next version 10.1 It is now available with changes that will interest both servers and desktop computers. Among the most noteworthy new features, The CodeReady Builder (CRB) repository is now enabled by default. And Btrfs support comes from the installation stage, accompanied by performance improvements, toolchain updates, and advancements in containers, virtualization, and security.
Although the headline focuses on 10.1, we must not lose sight of the groundwork laid by AlmaLinux 10, codenamed 'Purple Lion'. The distribution maintains ABI-level compatibility with RHEL It also adds its own features: frame pointer activation, expanded x86-64-v2 compatibility, Secure Boot support on ARM, the return of SPICE, and Live editions for GNOME, KDE Plasma, and Xfce. All of this is complemented by cloud images for major vendors and options for migrating from CentOS using the ELevate tool.
AlmaLinux 10.1, status and scope
Version 10.1 arrives as “Heliotrope Lion” for all supported architectures: x86_64, x86_64_v2, aarch64, ppc64le and s390x.
In addition to what was already present in AlmaLinux 10, version 10.1 incorporates Btrfs “end-to-end” support at the kernel and userspace levels, and allows the system to be installed directly on Btrfs from the installer. The team clarifies that the initial enablement focuses on the installer and the storage management stack, and that broader support within the AlmaLinux software collection will be rolled out gradually.
CRB enabled by default: goodbye to broken dependencies with EPEL
One of the most welcome practical changes is that, since AlmaLinux 10 and also in 10.1, the repository CodeReady Builder (CRB) comes enabled by defaultThis repository, known as PowerTools in Alma Linux 8.6It contains libraries and utilities that are not part of the RHEL/AlmaLinux base package, but are essential for development and dependency software that EPEL needs, including what is needed for environments like KDE Plasma.
Until now, many users encountered dependency errors when installing EPEL packages because CRB wasn't enabled, which caused frustration, unnecessary bug reports, and a steep learning curve. With the change, that friction disappearsNeal Gompa, a member of the AlmaLinux engineering committee, explained that the intention is that you no longer have to touch the repository configuration to install common packages such as plasma-discover o libAppStreamQt.
On systems already running AlmaLinux 10 (including the variant Kitten 10), the update adjusts the file almalinux-crb.repo setting enabled=1If you prefer to disable it, You can easily do it with dnf config-manager and reverse the option. This decision also paves the way for improved security: The selinux-policy-extra package will arrive within CRB, designed to improve EPEL software compatibility with SELinux and will be automatically installed during updates when CRB is active.
What is CRB and why does it matter?
CRB is a additional repository with libraries, SDKs and "glue" pieces which many applications take for granted. Its lineage comes from PowerTools (AlmaLinux 8), and its goal is to facilitate the development and deployment of software that, while not part of the RHEL core, This is critical for modern work environmentsHaving it active “out of the box” reduces incidents and prevents administrators from wasting time on mechanical activation and dependency resolution tasks.
Btrfs from the installer
Version 10.1 consolidates Btrfs support, which had already been tested in AlmaLinux OS Kitten since early September. Now, It is possible to install AlmaLinux directly on Btrfswith support enabled in both kernel and user space. The initial focus is on the installer and volume management, while the rest of the ecosystem will incorporate more advanced Btrfs capabilities as the cycle progresses.
This addition is relevant for those looking for snapshots, compression, or subvolumes without resorting to external solutions. Although the initial scope is conservative, the simple fact of being able to start with Btrfs from day one is a practical leap for testing, advanced desktops, and certain server scenarios.
Performance and toolchains up to date in AlmaLinux 10.1
AlmaLinux 10.1 also brings performance improvements and updates the developer toolsets with the latest versions of GCC, LLVM, and Rust. This results in more efficient builds, new optimizations, and greater compatibility with modern projects that point to those toolchains.
In addition, debugging and network utilities have been updated for polish daily experienceboth on servers and in development environments. Nothing revolutionary, but it does provide that "fine-tuning" that you notice when you're profiling, debugging, or load testing.
Containers and virtualization
On the containerization and virtualization front, AlmaLinux 10.1 introduces new versions of Podman, Buildah, Libvirt and QEMU-KVMThis combination ensures a more modern experience for building and running containers, as well as for managing them. hypervisors and virtual machines with less friction and better performance.
For those working with shared infrastructure, these version jumps matter: They improve compatibility, fix bugs, and often add small improvements quality of life improvements that accumulate over time. Furthermore, in the experimental setting, the KVM support preview for IBM POWER that users requested (including the OSL at Oregon State University), which expands the options in specialized hardware environments.
Security: SELinux, OpenSSL and SSSD policies
Security is not neglected. AlmaLinux 10.1 updates SELinux, OpenSSL, and SSSD policies to maintain the most robust, stable, and reliable systems. In parallel, the arrival of selinux-policy-extra inside CRB (once available) will strengthen the coexistence between SELinux and EPEL packages, a very common combination in servers and workstations.
If you manage fleets, these details are what make the difference in the medium term: Fewer permit issues, healthier libraries and a more predictable experience when you apply patches or incorporate new workloads.
Architectures and variants supported by AlmaLinux 10.1
The 10.1 covers x86_64, x86_64_v2, aarch64, ppc64le and s390xThis range allows deployment from conventional servers to high-performance mainframes and ARM systems. Furthermore, AlmaLinux 10, unlike RHEL 10, bet on expanding support for x86-64-v2 (when RHEL publishes binaries starting from x86-64-v3), with the idea of keeping somewhat older functional equipment in the security patch circuit for years.
To facilitate that path, the project is building an alternative variant of EPEL with compatibility for x86-64-v2. And in the ARM world, it has been added Secure Boot support, key for deployments where the verified boot chain is an essential requirement.
RHEL compatibility and the role of CentOS Stream
Since Red Hat's policy change regarding RHEL code, AlmaLinux has made its approach clear: It does not derive directly from RHEL code, but from CentOS StreamMaintaining compatibility at the ABI level. This means that software designed for RHEL runs correctly, preserving application interfaces, but with a different development model. focused on transparency and community.
In the project's own words, the goal is to support its community without compromising compatibility with RHEL 10, by introducing Specific improvements for those who need them And they know how to make the most of them. Among these improvements is the default activation of frame pointers, highly valued by developers for debugging and performance optimization.
Desktop, Live ISOs and user experience in AlmaLinux 10.1
For those who want to try before installing, AlmaLinux offers Live editions with GNOME, KDE Plasma and XfceThey make it easy to evaluate the system as a desktop, verify hardware compatibility, and make decisions without having to modify disks. Furthermore, the active CRB by default is noticeable when you install KDE Plasma components or utilities that use EPELbecause the typical dependency errors that disrupt the flow disappear.
As if that weren't enough, the project reintroduces drivers that Red Hat discardedexpanding hardware support, and recovers the SPICE protocol for remote desktops, absent since RHEL 9.0. This type of decision puts the focus on the usability without losing compatibility, a premise that the community has been valuing since the first versions.
Cloud imaging and AlmaLinux 10.1 deployments
AlmaLinux provides official images on major cloud providers. Amazon AWSThere are AMIs in the AWS Marketplace and as Community AMIs, and they are freeSpecific documentation and verification details are available in the project resources.
The Generic Cloud images They are published in the main mirrors and repositories, with verification and usage guides for running them on both local computers and servers; They are a flexible option for KVM, OpenStack, and private cloud or lab scenarios.
En Google CloudThe official images are available on the Marketplace and can also be deployed via gcloud CLI, with instructions available on the wiki. For Microsoft AzureThe project offers AlmaLinux 8.10 and 9.6 images available in all regions through the Azure Marketplace, with deployment from the store, portal, and CLI.
If you use OpenNebulaThere are also official images on the mirrors, with verification and usage guides. And in Oracle Cloud InfrastructureAlmaLinux publishes images in all regions through Oracle Cloud Marketplace, suitable for Regular, Shielded, and ARM instances, deployable from the Marketplace, Partner Image in the OCI console, and its own OCI CLI.
WSL, Raspberry Pi and additional formats
Beyond the cloud, AlmaLinux offers a battery of delivery formats which includes containers, images for WSL and for Raspberry Pi. This variety allows adopting the distribution in desktop, laboratory, CI/CD and IoT scenariosand maintain consistency between development and production environments.
Migrations from CentOS and upgrades between versions
If you come from 8.5 CentOSThe transition to AlmaLinux is straightforward thanks to the project's tools: The implementation of AlmaLinux allows for on-site migration Without reinstalling. For CentOS 7 and for jumps between major versions, Elevate (developed and maintained by the AlmaLinux community) enables migrations and major version upgrades “in situ”minimizing downtime and simplifying the path to a supported platform.
These routes are especially useful for organizations that need standardize without redoing entire deploymentsOr those who want to consolidate tools and repositories without surprises. As always, it's advisable to test first in staging environments and keep backups up to date.
Small details that improve everyday life
Returning to the core of the 10/10.1, there are small design decisions that become noticeable over the course of several weeks. reintroduction of controllers Red Hat has expanded compatibility with "salvageable" hardware, discarding hardware discarded by the company. default activation of frame pointers It facilitates performance profiling and diagnostics. And having an active CRB is one of those things that... Once you try them, you won't want to go back.especially if you use EPEL or desktops like KDE Plasma.
In virtualization environments, updating QEMU-KVM and Libvirt This typically translates to smoother VM lifecycles, better snapshot handling, and greater stability under load. And for teams that mix containers and VMs, Podman and Buildah daily They help ensure that the CI/CD chain does not fall behind upstream.
When to upgrade to AlmaLinux 10.1 and what to expect
If you are in production, you can now install the stable 10.1 to bring these improvements to mission-critical machines. Those already on AlmaLinux 10 will see some changes rolled out via updates (such as the CRB activation by default and its implications), and will be able to plan the adoption of Btrfs or the deployment of new toolchains according to internal policies.
AlmaLinux advances by combining RHEL compatibility, proprietary improvements and focus on usabilityCRB enabled by default simplifies daily life, Btrfs opens interesting doors from the installer, and toolchain, container, and security updates keep the stack modern.
