English
Magyar
On 24 November 2025, the AlmaLinux OS Foundation announced the general availability of AlmaLinux OS 10.1. This is the first minor release following 10.0, codenamed ‘Heliotrope Lion’, and it uses the 6.12.0-124.8.1.el10_1 kernel.
The installation ISOs are available in five versions:
- Intel/AMD (x86_64)
- For Intel/AMD (x86_64_v2) and older processors
- ARM64 (aarch64)
- IBM PowerPC (ppc64le)
- IBM Z (s390x)
AlmaLinux 10.1 improves performance, development tools and security: it introduces new compiler toolchains, updated module streams, better debugging and networking tools, as well as the latest versions of Podman and Buildah. In terms of security, the SELinux policy, SSSD and Keylime have been updated, whilst OpenSSL now supports post-quantum encryption.
Btrfs file system support
The 10th biggest new feature missing from RHEL is support for the Btrfs file system. Btrfs has been available in AlmaLinux OS Kitten since early September, and in version 10.1 both the kernel and user-space tools support it, meaning the system can be installed onto a Btrfs volume and booted from it. Btrfs snapshots and compression are particularly useful on a server, for example for taking a quick backup before an update. In the first phase, support has been added to the installer and the storage layer; it will be extended to the rest of the software collection at a later date.
Differences from RHEL 10.1
The AlmaLinux-specific additions introduced in version 10.0 have been retained in version 10.1:
- CRB repository enabled by default: for new installations, the CodeReady Builder (CRB) repository is enabled by default, so you no longer need to enable it separately to install the EPEL repository (
dnf install epel-release) - x86_64_v2 version: RHEL 10 requires an x86-64-v3 processor; AlmaLinux also produces a secondary v2 build, and EPEL covers this version as well
- Frame pointers are enabled by default for system-level profiling
- SPICE is once again available on both the server and client sides
- KVM on IBM POWER: the roll-out of KVM virtualisation on the IBM POWER architecture has continued
- Firefox and Thunderbird are available as standard RPM packages in the system repositories
- Legacy hardware: the aacraid, be2iscsi, be2net, hpsa, lpfc, megaraid_sas, mlx4_core, mpt3sas, mptsas, qla2xxx and qla4xxx drivers now recognise devices that were previously disabled in the upstream
Software versions in AlmaLinux 10.1
| Area | Versions |
|---|---|
| Languages and runtime environments | Python 3.12.11, Node.js 24 |
| Web server | Apache HTTP Server 2.4.63 |
| Basic toolchain | GCC 14.3.1, glibc 2.39, binutils 2.41, Annobin 12.99 |
| Compilers and toolkits | GCC Toolset 15 (GCC 15.1, Binutils 2.44), LLVM Toolset 20.1.8, Rust Toolset 1.88.0, Go Toolset 1.24 |
| Debugging and logging | GDB 16.3, Valgrind 3.25.1, SystemTap 5.3, Dyninst 13.0.0, elfutils 0.193, libabigail 2.8, bpftrace 0.23.5, rsyslog 8.2506.0 |
| Performance monitoring | PCP 6.3.7, Grafana 10.2.6 |
| Network | NetworkManager 1.54.0, iproute 6.14.0, ethtool 6.15 |
| Containers and virtualisation | podman 5.6.0, buildah 1.41.4, libvirt 11.5.0, QEMU-KVM 10.0.0 |
| Security | SELinux policy 42.1.7, SSSD 2.11.1 |
| Miscellaneous | Samba 4.22.4, Mesa 25.0.7 |
Post-quantum encryption and RPMv6 signatures
- Encryption policy: post-quantum (PQC) algorithms are enabled by default in all policies
- OpenSSL 3.5: supports the ML-KEM, ML-DSA and SLH-DSA algorithms; the hybrid ML-KEM key exchange has been added to the default TLS suites
- RPMv6 signatures: using Sequoia PGP tools, RPM packages can be signed using PQC algorithms, and OpenPGPv6 signatures can be generated and verified
ISO verification and updating
With the AlmaLinux 10 key, the ISO can be verified regardless of architecture:
wget https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux-10
gpg --import RPM-GPG-KEY-AlmaLinux-10
wget https://repo.almalinux.org/almalinux/10.1/isos/$(uname -m)/CHECKSUM
gpg --verify CHECKSUM
sha256sum AlmaLinux-10.1-$(uname -m)-boot.iso
The line “Good signature from ‘AlmaLinux OS 10’” (fingerprint: EE6D B7B9 8F5B F5ED D9DA 0DE5 DEE5 C11C C2A1 E572) and the SHA256 value matching the CHECKSUM file should appear. For the x86_64_v2 ISO, manually enter the directory name x86_64_v2 in place of $(uname -m), as the command returns x86_64 even on such a machine.
Existing AlmaLinux 10.0 systems can be updated using the dnf upgrade -y command. For users of the 10.1 beta:
dnf install https://repo.almalinux.org/almalinux/almalinux-{release,repos,gpg-keys}-latest-10.$(uname -m).rpm
dnf upgrade -y
The dnf upgrade command will not upgrade from AlmaLinux 9 to 10; it is worth checking the requirements for an in-place upgrade at the end of our ELevate guide and in the ELevate documentation.
The full list of changes can be found in the AlmaLinux 10.1 release notes and the Red Hat Enterprise Linux 10.1 release notes.
How long will AlmaLinux 10 be supported?
Active support for AlmaLinux 10 will continue until 31 May 2030, and security updates will be provided until 31 May 2035. Releases in the 10 series:
- AlmaLinux 10.0 (May 2025)
- AlmaLinux 10.2 (May 2026)
A week earlier, the point release of the 9 series, AlmaLinux 9.7, was released.
AlmaLinux is an optional operating system on both our KVM VPS servers and our dedicated servers. Our cPanel hosting servers, meanwhile, run CloudLinux OS, which is closely related to AlmaLinux and is also RHEL-compatible.