AlmaLinux
Overview
What is AlmaLinux OS
AlmaLinux OS is a free, open-source, community-owned and governed enterprise Linux distribution that serves as a binary-compatible alternative to Red Hat Enterprise Linux (RHEL). Established as a direct fork of RHEL source code, it emphasizes long-term stability and provides a robust, production-grade platform for mission-critical applications without reliance on proprietary vendor support.[1][4] This compatibility ensures that software packages, configurations, and binaries built for RHEL function seamlessly on AlmaLinux without modifications, allowing organizations to migrate or deploy applications with minimal disruption. AlmaLinux emerged in response to the transformation of CentOS into a downstream RHEL variant, filling the need for an independent, upstream-focused enterprise Linux option.[1][4] The distribution targets enterprises, developers, and server administrators who require a reliable operating system for servers, cloud environments, and development workflows, particularly those avoiding vendor lock-in through community-driven alternatives. It supports multiple architectures, including x86_64, aarch64 (ARM64), ppc64le, and s390x, enabling deployment across diverse hardware from standard Intel/AMD systems to IBM Power and mainframes.[1][4] Under the stewardship of the AlmaLinux OS Foundation, a 501(c)(6) non-profit organization, AlmaLinux commits to a forever-free model, ensuring perpetual access without subscription fees or end-of-life restrictions, backed by community contributions and corporate sponsorships.[1][4]Core Principles and Compatibility
AlmaLinux OS is guided by core principles centered on community ownership and governance through the AlmaLinux OS Foundation, a non-profit organization that ensures meritocratic decision-making and independence from corporate control.[1] This structure promotes transparency across all development processes, including public access to build artifacts, source code repositories on GitHub, and detailed documentation, allowing users and contributors to verify every aspect of the distribution.[5] Additionally, AlmaLinux commits to long-term support without subscription fees, providing enterprise-grade stability for up to 10 years per major release, while maintaining complete openness as a forever-free, open-source platform backed by diverse sponsorships.[1] A foundational commitment of AlmaLinux is its binary compatibility with Red Hat Enterprise Linux (RHEL), ensuring that applications and binaries built for RHEL run seamlessly on AlmaLinux without recompilation or modification.[1] This compatibility is achieved through ABI (Application Binary Interface) alignment, with source code synchronized from upstream projects like CentOS Stream and Fedora rather than direct RHEL rebuilds, a shift implemented in 2023 to adapt to changes in source availability while preserving functional equivalence.[6] Key features supporting this include full compatibility with RHEL source RPMs for package rebuilding, synchronization of errata for security updates and bug fixes to match RHEL's advisory cadence, and the provision of Software Bill of Materials (SBOM) for each release to enable transparent security auditing and supply chain verification.[7][8] Unlike RHEL, which incorporates proprietary elements and requires paid subscriptions for full support, AlmaLinux excludes all such components, focusing exclusively on open-source alternatives and community-driven enhancements.[9] Notable additions include support for the x86-64-v2 microarchitecture baseline in builds, extending compatibility to older hardware that RHEL has phased out.[10] As of 2025, AlmaLinux adheres to RHEL 10 compatibility standards, featuring kernel version 6.12.0 and a package ecosystem that mirrors RHEL 10's core libraries, tools, and dependencies for enterprise workloads.[3][11] The AlmaLinux build system plays a crucial role in upholding these guarantees by automating verification of binary outputs against upstream specifications.[6]History
Founding and Early History
On December 8, 2020, the CentOS project announced a strategic shift toward CentOS Stream as its primary development model, positioning it as an upstream rolling release ahead of Red Hat Enterprise Linux (RHEL), while traditional CentOS Linux would cease production after December 31, 2021.[12][13] This pivot raised concerns among users reliant on a stable, free RHEL-compatible distribution, prompting the need for an independent alternative to maintain enterprise-grade stability without upstream development risks.[14] In response, CloudLinux Inc. launched the AlmaLinux project on January 14, 2021, as a community-oriented initiative to create a 1:1 binary-compatible fork of RHEL, directly addressing the void left by CentOS Linux.[14] The project released its first beta version, AlmaLinux OS 8.3-beta (codenamed Purple Manul), on February 1, 2021, after approximately 1.5 months of development by CloudLinux engineers incorporating initial community feedback.[15] This beta emphasized seamless migration for CentOS users, with repositories hosted on repo.almalinux.org and development tracked via GitHub.[15] AlmaLinux's core objectives from inception were to deliver a forever-free operating system with 10-year support cycles per major release—aligning with RHEL's lifecycle to ensure predictable security updates and bug fixes through at least 2029 for the initial version—while remaining fully sponsored to avoid commercialization pressures.[14][16] CloudLinux committed $1 million annually as the founding sponsor, supplemented by contributions from partners like AWS and Azure, to fund infrastructure and operations.[14][1] Among the early hurdles were rapidly sourcing and repackaging source RPMs from CentOS Linux repositories ahead of their end-of-life to guarantee compatibility, alongside recruiting contributors through channels like GitHub, a project wiki, and webinars to build a diverse governance model.[17][15] Establishing autonomous build systems posed additional complexity, requiring validation of binary equivalence without direct Red Hat access, though CloudLinux's decade of RHEL repackaging expertise accelerated progress.[17] These efforts culminated in the first stable release of AlmaLinux OS 8.3 on March 30, 2021, simultaneous with the incorporation of the AlmaLinux OS Foundation as a 501(c)(6) nonprofit to transfer control from CloudLinux to community-led oversight, safeguarding against future acquisitions or shifts.[18][17]Key Developments and Milestones
In July 2022, the AlmaLinux OS Foundation introduced the AlmaLinux Build System (ALBS), an open-source infrastructure designed to enable independent rebuilding of the distribution from source code, thereby reducing reliance on external providers like CentOS Stream for package production.[19] This shift marked a pivotal step toward full autonomy, allowing the project to maintain binary compatibility with Red Hat Enterprise Linux (RHEL) while controlling its own development pipeline.[20] Project ELevate, launched in October 2021, provided a framework for in-place migrations between major versions of RHEL-based distributions, including upgrades from CentOS 7 to AlmaLinux 8 and subsequent intra-version transitions to 9 and 10.[21] By August 2024, significant updates expanded support to include migrations from CentOS 6, Scientific Linux 7, and CentOS Stream 8, while preserving user data and configurations.[22][23] These enhancements continued into 2025, with ongoing community-driven refinements to the Leapp utility and data libraries, including a November 3, 2025, update adding vendor support (e.g., Nginx, KernelCare, MariaDB, Imunify) for upgrades from AlmaLinux 9 to 10.[24] The release of AlmaLinux 9 on May 26, 2022, aligned closely with RHEL 9, incorporating kernel 5.14 and improvements in cloud, container, and web console functionalities.[25] AlmaLinux 10 followed on May 27, 2025, introducing kernel 6.12, Secure Boot for ARM platforms, and enhanced hardware support, solidifying the project's independence by leveraging ALBS for all builds without upstream dependencies.[10][11] In October 2025, the project announced the beta release of AlmaLinux 10.1, featuring performance improvements and updated developer toolsets including the latest GCC, LLVM, and Rust versions.[26] In May 2024, the AlmaLinux Engineering Steering Committee (ALESCo) was formed to oversee technical decisions, coordinate engineering efforts, and ensure long-term sustainability through community input on robustness and reliability.[27] This committee acts as a centralized body for guiding development priorities, including vulnerability responses and feature integration.[28] From 2024 to 2025, key initiatives included the October 22, 2024, introduction of AlmaLinux OS Kitten, a development branch serving as the direct upstream for future stable releases like AlmaLinux 10, enabling early testing for users and partners such as Cisco and Miracle Linux.[29] The project conducted community surveys, notably in June 2025, to gather user feedback on features and priorities without telemetry implementation.[30] AlmaLinux also participated in major conferences, including FOSDEM and CentOS Connect in January 2025, where representatives presented on ELevate upgrades and SIG developments.[31] Sponsorship expanded significantly, growing from 25 members in early 2024 to 34 by year's end, with additions like AMD, Fastly, and Virtuozzo providing infrastructure and financial support.[32][33] This growth continued in 2025, with renewals such as Cybertrust Japan as a Platinum Sponsor in June.[34] Board elections for the AlmaLinux OS Foundation were planned for August-September 2025 to select directors, emphasizing community governance, though the process was later rescheduled to March 2026 for procedural refinements.[35][36]Governance and Community
The AlmaLinux OS Foundation
The AlmaLinux OS Foundation was established in March 2021 as a 501(c)(6) non-profit organization based in the United States, specifically incorporated as a Delaware non-stock, nonprofit corporation.[1][37][38] It owns all assets related to AlmaLinux OS, including trademarks, build infrastructure, repositories, and other project resources, with initial assets transferred from CloudLinux, Inc., to ensure independent community stewardship.[37] The foundation's mission is to further develop and maintain AlmaLinux OS as a free, stable, open-source Linux distribution without registration or advertising requirements, while fostering community growth, promoting transparency, and ensuring the project's long-term viability for the benefit of users and contributors.[38][39] This includes supporting an ecosystem of vendors and partners, as well as pursuing board-approved activities to sustain the distribution's enterprise-grade compatibility and accessibility.[38] Governance is led by a Board of Directors, consisting of up to 13 members (typically at least seven), with Benny Vasquez serving as Chair as of 2025.[39][40] The board oversees major decisions via supermajority votes and includes directors such as Jack Aboutboul, Jesse Asklund, Simon Phipps, Moshe Bar, Daniel Pearson, Jun Yoshida, and Alex Iribarren, alongside non-voting expert David Snead.[39] Board elections occur periodically; the planned 2025 cycle, originally set to begin on August 31, was postponed to March 2026 due to procedural issues, using ranked-choice voting for three-year terms, with current board terms extended. Eligible members from classes including Platinum, Gold, Silver, Ruby, Contributor, Alumnus, and Mirror participate in nominations and voting.[41][36][38] Key committees, including the Membership Committee—which reviews applications and meets regularly—along with the Executive, Technical Steering, Vendor Selection, and optional Marketing Committees, support governance and operational needs.[39][38] Funding is derived from a tiered membership model, with fees ranging from $100,000 annually for Platinum members to $2,500 for Silver, as well as in-kind contributions such as employee time or hardware; this structure emphasizes independence, avoiding reliance on entities like Red Hat and instead drawing sponsorships from diverse companies including CloudLinux.[39][42] Membership classes grant varying voting rights, with good standing required for participation in electing community directors and influencing project direction.[38]Community Structure and Contributions
The AlmaLinux community operates through structured membership tiers that encourage participation at individual and organizational levels. Individual contributors qualify as Contributor Members by demonstrating active involvement, such as code submissions or documentation improvements, granting them one vote in board elections, the ability to nominate candidates, and usage of the Contributor logo on their profiles.[39] Sponsor tiers include Silver ($2,500 annual fee or equivalent in-kind contributions), Gold ($20,000), Platinum ($100,000), and Ruby ($5,000), each providing escalating voting rights—5, 15, 50, and 5 votes respectively—along with benefits like prominent logo placement on the project website, event promotions, and press release mentions to enhance visibility.[39] These tiers, managed by the project's Membership Committee, ensure broad representation in governance while supporting the foundation's neutrality.[39] Contributions flow through diverse channels that facilitate collaboration and feedback. Developers and users engage via Git repositories on platforms like GitHub for code reviews and pull requests, particularly in repositories such as almalinux-deploy for migration tools.[43] The official forums at forums.almalinux.org host discussions on general topics, support, and development, serving as a primary hub for community interaction.[43] Real-time communication occurs on chat.almalinux.org, a Matrix-based platform with channels like #almalinux for introductions and topic-specific rooms, supplemented by legacy IRC support.[44] Special Interest Groups (SIGs), such as the Cloud SIG for container and image work or the HPC and AI SIG for high-performance computing needs, enable focused collaboration on niche areas.[45] Bug reporting is centralized at bugs.almalinux.org, a GitLab instance where users file issues, while packaging contributions involve rebuilding RHEL packages or EPEL modules through the build system.[43][46] Key initiatives underscore the community's role in shaping the project. The annual community survey, such as the 2025 edition launched in June, gathers anonymous user feedback on usage patterns, support needs, and feature priorities to inform data-driven decisions without relying on telemetry.[30] Packaging efforts allow contributors to submit and maintain third-party repositories, integrating them into official channels like EPEL.[46] These activities, coordinated by the AlmaLinux OS Foundation, amplify grassroots input into development.[47] Engagement extends to events that build connections and showcase contributions. The community maintains booths and speaking slots at major conferences, including FOSDEM 2025 in February for open-source developers, All Things Open in October 2025 in Raleigh, North Carolina, and CloudFest USA in November 2025 in Miami, Florida, where foundation leaders discuss collaboration in AI and cloud ecosystems.[31][48] Developer meetups and webinars, hosted via the project's events platform, facilitate hands-on sessions and SIG discussions.[49] The community's impact is evident in influential feature decisions, driven by user feedback and SIG input. Secure Boot support, enabling trusted boot processes on Intel/AMD and ARM platforms, was prioritized and implemented in AlmaLinux OS 10 based on community demands for enhanced security.[10] Similarly, the addition of x86-64-v2 architecture in version 10.0 extended compatibility to older hardware, addressing SIG and survey-identified needs for broader hardware support without compromising modern optimizations.[3] Over 40 individual backers contribute via GitHub and Open Collective as of early 2025, reflecting growing grassroots involvement.[32]Technical Infrastructure
Project ELevate
Project ELevate was introduced in 2021 by the AlmaLinux project as an open-source toolset to enable in-place upgrades for systems running CentOS Linux 7 or 8, as well as other RHEL-based derivatives, to AlmaLinux versions.[21] It builds on Red Hat's Leapp utility and upgrade tools, providing a framework for seamless transitions while maintaining system stability.[50] The project has facilitated upgrades on over 500,000 devices worldwide, contributing significantly to the migration of users away from discontinued distributions like CentOS Linux following its end-of-life in 2021.[21] At its core, ELevate utilizes a Leapp-based framework to handle data migration, package replacement, and preservation of existing configurations, ensuring minimal disruption to applications and settings during the upgrade.[50] This includes support for third-party repositories such as EPEL (limited to AlmaLinux), Docker CE, MariaDB, nginx, PostgreSQL, Imunify, KernelCare, and TuxCare, allowing for comprehensive ecosystem compatibility.[50] The tool performs one-step upgrades for most paths, leveraging actors—modular components—for custom migration tasks, such as handling specific hardware or software adjustments.[51] Supported upgrade paths encompass CentOS 7 to AlmaLinux 8/9/10, CentOS 8 to AlmaLinux 8/9, and intra-version migrations like EL8 to EL9 or EL9 to EL10, with extensions enabling transitions to Rocky Linux 8 and Oracle Linux 8 equivalents from CentOS 7, and from Rocky Linux 8 to EL9; higher Oracle Linux versions use Oracle's Leapp utility.[21][50] For older systems, it also covers CentOS 6 to CentOS 7 using the Red Hat Upgrade Tool, and Scientific Linux 7 to AlmaLinux 8 with specific workarounds.[21] The usage process starts with installing the ELevate release package from the official repository, followed by the Leapp upgrade tools and AlmaLinux-specific data modules, such asleapp-data-almalinux.[51] Pre-upgrade checks are conducted via leapp preupgrade to generate a report identifying issues like incompatible packages or configurations, which must be resolved before proceeding.[51] The upgrade is initiated with leapp upgrade, triggering a reboot into a dedicated initramfs environment, after which post-upgrade verification involves checking release files (/etc/redhat-release and /etc/os-release), scanning for residual old packages, and reviewing logs in /var/log/leapp/.[51]
Despite its capabilities, ELevate has limitations, including the recommendation against direct production use without prior testing in a non-critical environment, and the requirement for offline upgrades in certain paths due to the reboot process.[51] It lacks support for Raspberry Pi images and does not enable x86_64_v2 architecture for upgrades to AlmaLinux 10 or Kitten 10; additionally, some EL9 packages may persist post-upgrade if unavailable in the target version.[51]
AlmaLinux Build System (ALBS)
The AlmaLinux Build System (ALBS) was launched in July 2022 as a fully open-source, reproducible infrastructure for constructing AlmaLinux OS packages, hosted at build.almalinux.org.[19] It provides public read-only access to build processes and logs, enabling verification of package integrity from source to distribution.[19] Developed under the GPLv3 license, ALBS replaced proprietary tools previously used in AlmaLinux's early releases, marking a shift toward greater community involvement in the build pipeline.[52] At its core, ALBS operates by pulling source code from upstream repositories, including CentOS Stream and Red Hat Enterprise Linux (RHEL) mirrors hosted on git.almalinux.org, to compile RPM packages.[53] The system then performs automated testing via the AlmaLinux Testing System (ALTS), signs packages with PGP keys for authenticity, and pushes verified outputs to public repositories.[53] This architecture supports multiple processor architectures, including x86_64, aarch64, ppc64le, and s390x, ensuring broad hardware compatibility.[19] Key objectives of ALBS emphasize transparency through public Git repositories and verifiable build artifacts, reproducibility via deterministic compilation environments, and enhanced security through integration with immudb for cryptographic notarization of each build step.[53] The workflow is typically triggered by upstream source changes or manual community requests, generating Software Bill of Materials (SBOMs) for component tracking and errata advisories for security patches and updates.[53][8] By 2025, ALBS supported builds for AlmaLinux OS 10, maintaining ABI compatibility with RHEL 10.[53][10]Build System Components
Git Service and Source Control
AlmaLinux's source code management is centralized on the git.almalinux.org platform, a self-hosted Git service powered by Gitea, which hosts repositories for the operating system's RPM package sources and related projects.[54][53] This service mirrors upstream sources primarily from CentOS Stream repositories, serving as the public access point for RHEL-related code following Red Hat's policy changes that restricted direct SRPM access.[6][52] The repositories ensure ABI compatibility with RHEL while accommodating AlmaLinux-specific customizations. The syncing process involves automated pulls of the latest changes from upstream CentOS Git servers to maintain alignment with evolving source code, supplemented by manual updates from packagers for AlmaLinux adaptations.[53][52] Community contributors and the AlmaLinux OS Team submit patches, bug fixes, and feature enhancements directly through Git pull requests, with versioning achieved via commit tags that track package iterations.[52] These sources feed into the broader build pipeline, enabling reproducible package creation without delving into compilation details. As of 2025, the platform supports thousands of repositories, including modular content integrations like EPEL for additional package ecosystems.[53][55] Security is integral to the Git service, with every commit notarized using immudb, an immutable ledger that generates unique cryptographic hashes for tamper-proof verification of source integrity.[52] This notarization process stores metadata in a verifiable database, allowing public audits to confirm the authenticity of code changes and prevent unauthorized alterations.[52] The Gitea-based interface facilitates issue tracking, merge requests for collaborative reviews, and CI/CD triggers that integrate with the AlmaLinux Build System for automated workflows.[54][52] Public access to all repositories promotes transparency and community oversight in the development process.Build and Test Systems
The AlmaLinux Build System (ALBS) employs dedicated build nodes to compile RPM packages from source code stored in Git repositories. These nodes utilize the albs-node tool, which automates the fetching of build tasks from the ALBS Master Service and performs compilations in isolated environments using Mock and Docker containers.[56][53] The albs-node tool processes sources from git.almalinux.org, supporting builds from SPEC files, any Git reference, or third-party src.rpm files, and handles multiple concurrent builds (default maximum of four, configurable via settings). Upon successful compilation, the resulting RPM artifacts and build logs are uploaded to the PULP repository in the Artifact Storage system, where only notarized and verified builds are retained for further use.[56][53] Package validation occurs through the AlmaLinux Testing System (ALTS), an automated framework that executes tests on dedicated test nodes across supported architectures. ALTS leverages Docker and OpenNebula environments to create clean, isolated test instances, enabling checks for package integrity, installation, and functionality via custom or third-party scripts.[57][53] Builds in ALBS are triggered via the Master Service API following synchronization of source code from Git repositories, ensuring that compilations reflect the latest committed changes. Subsequent testing in ALTS encompasses unit tests, integration tests, and regression tests tailored to specific architectures; any failures during these stages halt the pipeline progression, with results and logs stored in Artifact Storage for review and reporting via the project's issue tracker.[53][57] For scalability, albs-node instances can be deployed across multiple machines to enable parallel processing of build tasks, with resource management handled through Docker orchestration to support efficient handling of large package sets. As of 2025, the system includes support for the x86-64-v2 baseline, providing compatibility for older hardware alongside newer microarchitectures like x86-64-v3 in AlmaLinux OS 10.[56][10] Quality assurance is enhanced during the build phase through the generation of Software Bill of Materials (SBOM) records using the alma-sbom utility, which creates standardized CycloneDX or SPDX documents from build artifacts for subsequent vulnerability scanning and supply chain verification. These SBOMs are derived from notarized build data stored in immudb, ensuring transparency and traceability of package components.[58][59][8]Release System and Signing
The Release System in the AlmaLinux Build System (ALBS) handles the final distribution of validated and signed RPM packages by uploading them to public repositories, such as repo.almalinux.org, ensuring availability for users worldwide.[53] After packages pass testing and verification, the system processes release tasks to manage updates and incremental changes, pulling the latest modifications from source repositories to generate new package sets.[53] This step finalizes the packaging stage, preparing artifacts for deployment without altering the underlying build or source control processes. The Sign Server component secures these packages using PGP keys to sign RPMs, emulating the standard rpmsign process through Python-based automation.[60] Each signing operation verifies prior notarization, applies the PGP signature, and re-notarizes the signed package by storing a unique hash in immudb, an immutable database that ensures tamper-proof traceability for every build step.[53] The server supports GPG signatures for package integrity and includes SHA checksums as part of RPM metadata verification, with signed packages then stored in Artifact Storage before release.[61] Upon post-test approval, the signing process is triggered automatically, followed by the creation of errata to document security fixes, bug resolutions, and enhancements for user notification.[62] Minor updates are handled through automated workflows that rebuild and sign packages based on git changes, streamlining the pipeline for ongoing maintenance.[53] Errata are published via dedicated channels, prioritizing security advisories to inform users of critical patches.[61] As of 2025, the system integrates Secure Boot key support, with kernels and bootloaders signed using keys generated in 2024 and valid through subsequent years, enabling verified booting on compatible hardware since AlmaLinux 8.4.[63][61] Transparency is enhanced through multi-key management in the Sign Server, allowing multiple PGP keys to be registered and used for signing tasks, as facilitated by the ALBS API.[64] This API, exposed via the web server, supports custom releases by enabling programmatic creation, updating, and committing of release plans with specified builds and platforms.[64] Distribution extends beyond RPMs to include installation ISOs, cloud images for providers like AWS, Google Cloud, and Azure, and container images compatible with OCI runtimes such as Docker and Podman, all pushed to a global network of mirrors for efficient access.[65][1] These artifacts are synchronized across mirrors shortly after signing, supporting architectures like x86_64, aarch64, ppc64le, and s390x.[66]AlmaLinux OS Kitten
Purpose and Introduction
AlmaLinux OS Kitten is an experimental, non-production Linux distribution launched on October 22, 2024, by the AlmaLinux OS Foundation, built from CentOS Stream 10 sources to enable early testing of features destined for AlmaLinux OS 10.[29] As a development-focused preview, it serves as a direct upstream for the stable AlmaLinux releases, allowing the community to engage in the release process ahead of time and influence its direction.[67] The primary purpose of Kitten is to offer downstream developers and power users an early glimpse into upcoming enhancements, including x86-64-v2 microarchitecture optimizations for improved performance on modern hardware, re-enabled frame pointers for better debugging, and new kernel features such as Secure Boot support and KVM enhancements for IBM POWER architectures.[29] Unlike the mainline AlmaLinux distributions, Kitten tracks CentOS Stream 10 as an upstream preview that informs AlmaLinux development, but it undergoes limited stability testing and is not recommended for production environments.[29] ISOs and package repositories are hosted at kitten.repo.almalinux.org, making it suitable for continuous integration/continuous deployment (CI/CD) pipelines, personal experimentation, and third-party project validation, with images rebuilt quarterly and frequent package updates.[29] As of November 2025, AlmaLinux OS Kitten 10 continues to track upstream CentOS Stream 10 developments, having played a key role in validating the AlmaLinux 10.0 stable release issued on May 27, 2025.[67] It provides an ongoing preview for community feedback and testing, including early features like Btrfs filesystem support (available since September 2025 ahead of the AlmaLinux 10.1 beta in October 2025), Raspberry Pi images (April 2025), and ELevate migration paths from AlmaLinux 9 (July 2025).[68][69][70]Build Pipeline Integration
AlmaLinux OS Kitten operates within the AlmaLinux Build System (ALBS) through a dedicated branch that facilitates its role as a development preview for AlmaLinux OS 10. This separate branch pulls source code directly from CentOS Stream 10, serving as the upstream foundation for Red Hat Enterprise Linux 10, and applies AlmaLinux-specific patches to enable features such as re-enabled frame pointers for improved debugging and tracing, SPICE protocol support for virtual machine graphics, and compatibility for over 150 device drivers previously dropped in upstream sources.[29][67][53][71] The technical setup extends ALBS to include an x86-64-v2 baseline alongside the default x86-64-v3, targeting broader hardware compatibility, while incorporating custom test suites via the AlmaLinux Testing System (ALTS) to validate these preview features on various nodes, including Docker and OpenNebula environments. Validated changes from Kitten are fed back to the mainline AlmaLinux OS through community-contributed patches submitted via git repositories on git.almalinux.org, creating a feedback loop where issues identified during testing—such as security vulnerabilities or compatibility gaps—directly inform enhancements in stable releases. This process also supports modular extensions, allowing community members to test and integrate additional packages without disrupting the core pipeline.[53][71][72] However, Kitten builds lack long-term support, remaining ephemeral and intended solely for development and testing until features are stabilized and promoted to mainline releases.[29][67][71]Releases
Major Versions
AlmaLinux OS 8, the initial stable release series, was first made available on March 30, 2021, as version 8.3, serving as a direct binary-compatible replacement for CentOS Linux based on Red Hat Enterprise Linux (RHEL) 8.[16] This series emphasized enterprise-grade stability for servers and workstations, with ongoing updates to address security and bug fixes. The latest minor release, 8.10 (codename Cerulean Leopard), arrived on May 28, 2024, incorporating kernel updates to version 4.18.0-553 for improved hardware support and performance optimizations. AlmaLinux OS 9, released starting with version 9.0 on May 17, 2022, maintains full compatibility with RHEL 9 and introduces enhancements for modern desktop and multimedia environments, including Wayland as the default display server for GNOME and PipeWire as the primary audio and video handling framework.[73][74] These changes enable better integration with contemporary hardware and applications, such as improved graphics rendering and low-latency media processing. The most recent update, 9.6 (codename Sage Margay), was issued on May 20, 2025, featuring kernel 5.14.0-570.12.1 along with bolstered security measures like updated cryptographic policies and SELinux enhancements. As of November 16, 2025, 9.7 beta (codename Moss Jungle Cat) was released on October 8, 2025.[75] AlmaLinux OS 10, dubbed "Purple Lion," debuted with version 10.0 on May 27, 2025, built upon RHEL 10 and incorporating kernel 6.12.0-55.9.1 for advanced system efficiency and broader hardware compatibility.[10][3] Key additions include support for the x86-64-v2 baseline to accommodate older x86_64 processors, Secure Boot implementation across Intel/AMD and ARM architectures to prevent unauthorized boot-time modifications, SPICE protocol integration for enhanced remote desktop and virtualization scenarios, and updated database servers including MariaDB 10.11, MySQL 8.4 (via the mysql8.4-server package in repositories such as AppStream), PostgreSQL 16, and Valkey 8.0. Oracle MySQL 8.4 can also be installed using the official MySQL Yum repository for el10-compatible systems.[3][76] As of November 16, 2025, 10.1 beta (codename Heliotrope Lion) was released on October 21, 2025.[26] Minor releases across all major versions follow a pattern of approximately every six months, aligning closely with RHEL's schedule to deliver bug fixes, errata, and package updates; for instance, betas for 9.7 and 10.1 emerged in October 2025.[77][78] Each minor version reaches end-of-life upon the subsequent release's availability, with full support timelines extending active maintenance for about five years followed by five years of security updates only.[78] Installation media for AlmaLinux major versions include minimal, server, and workstation variants, alongside community spins such as GNOME, KDE Plasma, XFCE, and MATE desktop environments for live and installable ISOs.[65] Cloud-optimized images are provided for platforms like AWS, Azure, and generic cloud-init environments, facilitating seamless deployment in virtualized and public cloud infrastructures.[79][65]Support Lifecycle
AlmaLinux OS follows a 10-year support lifecycle for each major version, providing security updates and bug fixes to align with the upstream Red Hat Enterprise Linux (RHEL) model.[80] This commitment ensures long-term stability for enterprise users, with support divided into an active phase for comprehensive updates—including bug fixes, enhancements, and security patches—and a subsequent security-only phase focused on critical vulnerabilities.[77] The active phase lasts five years from RHEL's general availability, transitioning to security support for the remaining five years until end-of-life (EOL). For AlmaLinux OS 8, released in March 2021, active support concluded on May 31, 2024, with security support extending until May 31, 2029. AlmaLinux OS 9, generally available in May 2022, maintains active support until May 31, 2027, followed by security support through May 31, 2032.[81] AlmaLinux OS 10, released in May 2025, offers active support until May 31, 2030, and security support until May 31, 2035.[82] Each minor version reaches EOL upon the release of the subsequent minor version, ensuring users receive timely updates to the latest point release within the major version's lifecycle.[77] Post-EOL, while official support from the AlmaLinux OS Foundation ends, community-driven efforts may provide security fixes if critical needs arise, and third-party vendors offer commercial extended support options.[78] Users are recommended to migrate to newer versions using tools like ELevate, which facilitates in-place upgrades between major releases such as from AlmaLinux 8 to 9 or 9 to 10.[21] Support updates and errata, including security advisories and bug fixes, are tracked at errata.almalinux.org, with Software Bill of Materials (SBOMs) generated for each release to aid compliance and supply chain security assessments.[62][59]Azure Integration and Endorsement
In October 2024, AlmaLinux was officially designated as an Endorsed Linux Distribution on Microsoft Azure, joining a select group of distributions with this status from Microsoft. This recognition follows collaborative engineering efforts between the AlmaLinux OS Foundation and Microsoft, building on AlmaLinux's availability in the Azure Marketplace for over three years.[83][84] As an endorsed distribution, AlmaLinux provides smoother official images in the Azure Marketplace for x86_64 and Arm64 architectures (including support for Microsoft's Cobalt 100 VMs), enhanced testing with Microsoft tools, and strong integration for Azure Virtual Machines. This includes robust support for cloud-init provisioning to enable automated and scalable deployments, as well as compatibility with Azure's hybrid identity services for seamless authentication and management. These features deliver practical advantages in cloud-heavy workflows, as documented in Microsoft Azure resources and supported by community experiences.[85] AlmaLinux maintains full ABI and binary compatibility with Red Hat Enterprise Linux, ensuring application portability and ecosystem consistency. The distribution frequently provides security patches rapidly—often addressing vulnerabilities faster than upstream for lower-priority issues—while preserving complete compatibility and stability.Troubleshooting
DNS Resolution Failures
Users of AlmaLinux may encounter the error "Could not resolve host: mirrors.almalinux.org" with curl error 6 during DNF or YUM operations, such as system updates or package installations. This indicates a DNS resolution failure that prevents access to the AlmaLinux mirror list. The issue is typically local, arising from DNS configuration, network connectivity problems, or environment-specific factors (such as containers, virtual machines, system upgrades, or NetworkManager conflicts), and does not reflect any outage or malfunction with the AlmaLinux mirrors themselves. To troubleshoot and resolve this issue:- Test basic connectivity: Execute
ping 8.8.8.8to verify IP-level routing. - Test DNS resolution: Run
nslookup mirrors.almalinux.orgordig mirrors.almalinux.orgto check hostname resolution. - If resolution fails, temporarily add public DNS servers to
/etc/resolv.conf(e.g., add the linesnameserver 8.8.8.8andnameserver 1.1.1.1), then restart networking withsystemctl restart NetworkManageror reboot the system. - Check for additional causes: Verify no firewall blocks on UDP port 53, review proxy configurations, and investigate potential IPv6 issues.
- In specific cases (e.g., during upgrades or in containerized environments), confirm the network setup or temporarily disable NetworkManager for testing.
/etc/resolv.conf may be overwritten by dynamic network management services; for persistent changes, configure DNS settings through NetworkManager or the relevant interface configuration files.
