Learn Rocky Linux - Rocky 10, Lifecycle & Roadmap

#Introduction

In the previous episode 20, you mastered containers with Podman, Buildah, and Skopeo. Now we look ahead: where Rocky Linux stands today, where it's going, and how you plan for long-term use. This episode covers Rocky Linux 10, its lifecycle model, and the ecosystem roadmap.

Understanding lifecycle isn't just theoretical knowledge. It drives practical decisions: when to upgrade, how long a version is safe to use, and when to start planning a migration. A good sysadmin always knows which phase their system is in.

#Rocky Linux 10

#Main Features

Rocky Linux 10.0 was released in June 2025, based on RHEL 10. The latest minor release, 10.2, arrived in May 2026. Some key changes:

• DNF5 as the default — the package manager you've used since episode 4 becomes the full default.
• AppStream package modularity — the module streams model from episode 5 matures further.
• Kernel from the RHEL 10 branch — a stable 6.x kernel tested for the enterprise.
• More mature bootc/image mode — the image mode from episode 18 is increasingly fully supported.
• OpenSSH 9.x — a major update to the remote access foundation from episode 15.

cat /etc/rocky-release

dnf5 --version
uname -r
cat /etc/os-release

These three commands are the standard identity check: the release version, the dnf5 version, and the kernel version — a combination that proves the system is running on the Rocky 10 track.

#Supporting Multiple Versions

It's important to understand that Rocky 10 doesn't erase previous versions:

curl -s https://rockylinux.org/10/releases | grep -o '10\.[0-9]' | sort -u

curl -s https://endoflife.date/rockylinux

The EOL schedule is a reference you should check periodically — it determines when a system must be migrated.

#Lifecycle and Support

#The Support Model

Rocky Linux follows the RHEL lifecycle: every major release is supported for 10 years in total, split into two phases:

• Full Support (first 5 years) — feature updates, security fixes, and full bug fixes.
• Maintenance Support (next 5 years) — focus on security fixes and critical bugs.
• ELS (Extended Lifecycle Support) — optional beyond the 10 years, for organizations that need a longer transition window.

dnf5 check-update

#Minor Releases and Schedule

Minor releases arrive roughly every 6 months. For Rocky 10, the current rhythm looks like this:

Each minor release carries security updates and device updates merged from RHEL. Systems that follow the latest minor release are always on the fully supported track.

#Migrating from Rocky 9 to 10

#Preparation

A major version migration is a serious operation. The key preparations: a full backup (remember LVM snapshots from episode 8), a record of installed packages, and confirmation that applications are compatible with the new version.

#DNF5 System-Upgrade

Rocky provides an in-place migration path through the system-upgrade plugin:

dnf5 install dnf5-plugin-migrate

dnf5 remove epel-release

dnf5 system-upgrade --releasever=10 download

dnf5 system-upgrade reboot

This sequence downloads all packages for Rocky 10, then reboots straight into the upgrade process. Important note: once the system is on Rocky 10, reinstall EPEL for the new version — the same pattern you learned in episode 5.

#Backup Path

If an in-place migration feels too risky, there's always an alternative: a fresh install on a VM or bare metal (episode 3), then move the workload over. Many organizations choose this route for critical servers — a clean install is easier to debug than a complicated major upgrade.

#Roadmap

#Rocky 9 in Maintenance

Rocky Linux 9.x isn't disappearing — it enters the maintenance phase. Those of you still on Rocky 9 continue to receive security fixes and critical bug fixes until the end of its support period. Migrating to 10 isn't a sudden obligation, but a planned decision.

#Cloud-Native Focus

Rocky Linux's development direction is increasingly clear: cloud-native. The focus areas:

• Cloud images optimized for each major provider.
• Image mode (episode 18) as the modern way to manage OSes.
• Ecosystem integration — compatibility with Docker, Kubernetes, and container orchestration.

skopeo inspect docker://quay.io/rockylinux/rockylinux:10

With this direction, the skills you gathered in episodes 18 and 20 — image mode, bootc, Podman — aren't just course material; they're skills aligned with the platform's future.

#Closing

In this episode 21, you understood Rocky Linux's current position: the main features of Rocky 10 based on RHEL 10, the 10-year lifecycle model with minor releases around every 6 months and optional ELS, the Rocky 9 to 10 migration path with dnf5 system-upgrade, and the cloud-native roadmap focused on cloud images, image mode, and ecosystem integration.

Key takeaways:

• Rocky 10 (currently 10.2) brings default dnf5, the RHEL 10 kernel, and mature image mode.
• Lifecycle: 10 years of support, with a minor release every ~6 months and optional ELS.
• In-place migration uses dnf5 system-upgrade; a fresh install remains a safe alternative path.
• Rocky 9 stays supported in maintenance; migration is a planned decision.
• The roadmap moves toward cloud-native: image mode, cloud images, and the container ecosystem.

In the next episode 22, the final episode of this series, we will discuss ecosystem, alternatives, and final reflection — comparing Rocky Linux with AlmaLinux, Oracle Linux, CentOS Stream, and RHEL, when to choose which, a recap of all 22 episodes, and a production readiness checklist. See you in the closing chapter!