On 21 June 2023, Red Hat announced that it would no longer publish the source code of RHEL (Red Hat Enterprise Linux) on git.centos.org. From now on, the public source will be CentOS Stream, and the exact source of the packages released in RHEL will only be available to subscribers, under the terms of the subscription agreement. The announcement caused a storm, because AlmaLinux, Rocky Linux and several other RHEL-compatible distributions had been built from this source until now.
In the month since the announcement, all the major players have said what they plan to do. In this article we sum up what happened and what it all means if you run AlmaLinux or Rocky Linux servers.
What exactly happened to the RHEL source?
RHEL is made up of open-source software, and Red Hat has to make the source of the GPL-licensed parts available to the recipients of the binary packages. Until now, Red Hat did more than that: it published the source of every RHEL package openly, in a form that was easy to rebuild. This made it possible to build “1:1” clones – first CentOS Linux, then, from 2021, after CentOS Linux 8 was discontinued, AlmaLinux and Rocky Linux.
CentOS Stream is not the same thing. It is the development version of the next RHEL point release: packages appear here before they reach RHEL, but the exact package versions of a given RHEL release and the fixes backported to older branches are not necessarily visible in it.
The events of the past month
| Date | Event |
|---|---|
| 21 June 2023 | Red Hat announces that CentOS Stream will be the only public repository for RHEL-related sources. |
| 26 June 2023 | Red Hat responds to the criticism: in its view, RHEL has not become closed source, and the change is aimed at distributions that merely rebuild it. |
| 29 June 2023 | Rocky Linux states that it will obtain the sources from the RHEL-based UBI container images and from pay-as-you-go RHEL instances running in the cloud. |
| 10 July 2023 | Oracle criticises the decision in a blog post and says that Oracle Linux will remain RHEL-compatible. |
| 11 July 2023 | SUSE announces that it is developing its own RHEL-compatible distribution and will invest more than $10 million in it over the coming years. |
| 13 July 2023 | AlmaLinux announces that it is giving up 1:1 parity and is aiming for binary (ABI) compatibility instead. |
What does this mean for AlmaLinux?
Under the AlmaLinux foundation’s decision, AlmaLinux will in future be binary compatible with RHEL, but not necessarily identical to it package by package. In practice, this means:
- Applications built for RHEL will keep running on AlmaLinux; that is the point of binary compatibility.
- The sources are put together from CentOS Stream, the upstream projects and AlmaLinux’s own patches. For every patch it brings in from elsewhere, AlmaLinux states where it came from.
- AlmaLinux may fix a bug before RHEL does, or there may be small differences in individual packages. For bug reports, the foundation asks users to try to reproduce the bug in CentOS Stream as well, so that the fix ends up in the right place.
On most servers – web server, database, email, control panel – you won’t notice any of this. It may matter where a vendor certifies its product specifically for package versions identical to RHEL.
What does this mean for Rocky Linux?
Rocky Linux is keeping its original goal, packages identical to RHEL, but it obtains the sources in a roundabout way: from the freely downloadable UBI container images and from RHEL instances billed by the hour in the public clouds. According to the project, this lets it access the sources without accepting Red Hat’s terms of use, but it has also said that the method may change.
Whether this is sustainable in the long run, and how Red Hat will respond to it, is not yet known. This uncertainty is the biggest difference between the two projects.
Do you need to do anything now?
In short: there’s no need to rush. Existing AlmaLinux and Rocky Linux installations work and receive updates just as they did a month ago. AlmaLinux 8 promises security fixes until 2029 and AlmaLinux 9 until 2032 – we wrote about this in detail when AlmaLinux 9 was released, on the blog of our hosting brand, aWh.
What’s worth doing now:
-
Take an inventory. Which distribution and version runs on which server? On most systems, this shows it:
cat /etc/os-release rpm -q --whatprovides redhat-release - Check your critical software. If a vendor (control panel, database, backup software) officially supports only RHEL but has so far also accepted AlmaLinux or Rocky, follow what it says after the change.
- Watch the pace of updates. The most important question is whether security fixes arrive as quickly as before. Within a few months, anyone can check this for themselves.
- Don’t start a hasty migration. A rushed distribution switch is a bigger risk than waiting a few months.
What are the alternatives?
If you are making a decision for a new project now, you can choose from these:
| Option | When is it a good choice? |
|---|---|
| AlmaLinux | If you need a free, community-run, RHEL-compatible system and exact package parity is not a requirement. |
| Rocky Linux | If 1:1 parity is important and you accept the uncertainty around how the sources are obtained. |
| RHEL | If you need vendor support and certifications. Red Hat’s free developer subscription can be used by individuals on up to 16 machines. |
| Oracle Linux | If you need a free, RHEL-compatible system and Oracle is acceptable as a vendor. |
| CentOS Stream | For development, testing, and trying out the next RHEL version in advance. |
| Debian, Ubuntu LTS | If you are not tied to the RHEL world and your software supports them. |
On hosting servers, the control panel decides: cPanel, for example, supports only certain RHEL-based and Ubuntu versions, and CloudLinux is itself RHEL-based. If your environment hasn’t changed since the move to CloudLinux 8, there’s nothing to do there for now either.
The longer-term lesson
After the early end of CentOS Linux 8 in 2021, this is the second time a vendor’s decision has shaken infrastructures built on RHEL clones to their foundations. The lesson is not that you have to switch distributions immediately, but that servers need to be easy to reinstall: with settings described through configuration management (for example Ansible), regular and tested backups, and documented dependencies. If a server can be rebuilt on another distribution in a day, an announcement like this is an inconvenience, not a crisis. We have also written about handling end-of-life systems or systems with an uncertain future in our article on EOL strategies.
We help with designing Linux servers, switching distributions and automating configurations; you can read more about this on the Infrastructure and operations page.