Skip to content
Rocky Linux Community Docs
Rocky Linux
Docs networkNetwork
Search Rocky Linux

    Browse this documentation

    How Rocky Linux Differs from RHEL

    Rocky Linux targets bug-for-bug compatibility with RHEL — not just matching features, but matching known bug behavior as well. This page does not repeat the compatibility strategy and governance overview (hub-site view); it lists only the differences you actually hit in daily operations.

    Compatibility boundary: what transfers and what doesn’t

    Section titled “Compatibility boundary: what transfers and what doesn’t”
    DimensionInterchangeable with RHEL?Notes
    RPM packages / ABI / API✅ YesRHEL RPMs install directly on Rocky; ABI/API identical
    dnf / rpm package management✅ YesCommands, repo configuration and module streams behave the same
    systemd / SELinux / kernel tuning✅ YesService management, security policy and tuning skills transfer
    System behavior✅ IdenticalUnder the bug-for-bug goal, even known defect behavior aligns
    Red Hat subscriptions / certification ecosystem❌ NoRHEL subscription entitlements, commercial certification lists and some vendor support agreements do not travel with the packages
    Distro identity and trademarks❌ DifferentRelease files, branding and logos are Rocky’s own (below)

    Distro identity differences

    Section titled “Distro identity differences”

    Rocky ships its own release identity; scripts that hardcode redhat-release need attention:

    Check the release identity
    $ cat /etc/rocky-release          # Rocky Linux release 9.x
    $ cat /etc/redhat-release         # compatibility symlink, still readable in most cases

    Third-party scripts that parse /etc/redhat-release should be re-checked after migration — Rocky keeps the compatibility symlink, but the string content is Rocky’s.

    Subscription and repository differences

    Section titled “Subscription and repository differences”

    RHEL attaches content through a subscription; Rocky has no subscription concept — repositories work out of the box. When migrating from RHEL, unregister the subscription and clean the local credentials on the source system first, then run the conversion (subscription commands per Red Hat’s subscription documentation).

    Rocky’s repository tiers (baseos / appstream / crb / extras, plus the Rocky-specific plus repo) and how to enable them: see repository configuration.

    Source and build differences

    Section titled “Source and build differences”

    RHEL sources are published by Red Hat; after Red Hat restricted direct RHEL SRPM access in 2023, Rocky rebuilds from CentOS Stream git repositories, UBI containers, SRPMs obtained via compliant subscriptions, and other public sources — all under open-source license compliance. For builds, Rocky uses its own open-source cloud-native build system Peridot (rather than Fedora/CentOS Koji) to guarantee build transparency and independent auditability. Full background on both: the hub site’s Rocky Linux topic page.

    When to pick Rocky, when to pick RHEL

    Section titled “When to pick Rocky, when to pick RHEL”
    • Pick Rocky: free, RHEL binary-compatible production systems; CentOS migration targets; container hosts; research and education; EL ecosystem without subscription fees.
    • Pick RHEL: compliance/procurement hard-requires RHEL; dependence on Red Hat certification lists, first-party support SLAs or specific ISV certifications; Red Hat ecosystem add-ons.
    Section titled “Related pages”