Skip to main content

Convert CentOS 8 to AlmaLinux 8: A Practical Guide

Convert CentOS 8 to AlmaLinux 8: Enterprise server with its outer shell changing around an intact data core and a nearby backup archive

A server can keep running long after its update path has become a problem. To convert CentOS 8 to AlmaLinux 8, first establish exactly what the server runs and how you will recover it. Renaming a release package or pointing repositories somewhere new is not a complete migration plan.

CentOS Linux 8 reached end of life on December 31, 2021. Its archived packages do not provide ongoing CentOS Linux security maintenance. This guide covers a same-major distribution conversion to AlmaLinux 8, not an upgrade from CentOS 7 or a jump to AlmaLinux 9.

Convert CentOS 8 to AlmaLinux 8: Identify CentOS Linux versus CentOS Stream

cat /etc/os-release
uname -r
uname -m
sudo dnf repolist --enabled

Read the distribution identity and version, not just the kernel string. The current AlmaLinux deployment repository lists CentOS Linux 8.4 or later among supported sources. CentOS Stream has a different package history and its own documented conversion options. Do not apply the CentOS Linux procedure unchanged to a Stream system.

Review the official tool’s supported platforms, architecture and boot requirements for the actual host. A control panel, managed hosting image or specialist application can impose additional vendor requirements; confirm those before using a general distribution tool.

Choose conversion or a clean replacement

An in-place conversion may suit a compatible, understood server. A fresh AlmaLinux installation followed by a tested application transfer may be easier to validate when the source is heavily customized, badly outdated or difficult to recover.

Before you convert CentOS 8 to AlmaLinux 8, identify whether the source is CentOS Linux or CentOS Stream.

Neither approach guarantees that third-party software will keep working. Inventory enabled repositories, package exclusions, kernel modules, database engines, application runtimes, mounts, firewall rules and scheduled jobs. Identify which vendor owns support for each important dependency.

Prepare a recovery plan before package changes

  • Keep a recoverable system image or snapshot and application-consistent backups.
  • Store recovery data outside the server and test restoration.
  • Confirm provider or hypervisor console access, not only SSH.
  • Schedule downtime and record an explicit rollback decision point.
  • Rehearse against a representative isolated copy when possible.

Snapshots are not automatically database-consistent, and a backup stored on the same disk may disappear with that disk. Record what each recovery method actually restores. Prefer a stable console session; when using SSH, the official tool guidance recommends a terminal multiplexer such as screen or tmux.

Update and resolve repository problems carefully

The official workflow calls for updating the source system and rebooting when needed. Review the proposed transaction rather than making unattended package changes on a production host:

sudo dnf update
sudo reboot

On an old CentOS installation, this can fail because standard mirrors no longer serve the release. Stop and read the deployment tool’s current CentOS 8 migration notes. Its documented -f option addresses specific update and repository issues, but it is not a universal repair flag.

Do not blindly replace every repository URL, disable signature verification or remove conflicting packages without understanding their role. An archived source repository can assist a controlled migration; it does not make the source operating system maintained again.

Do not convert CentOS 8 to AlmaLinux 8 until the chosen tool supports the source system and a recovery plan is ready.

Download and inspect the official AlmaLinux tool

Use the AlmaLinux-owned repository, check its current README and retain the exact script you reviewed. Its main branch can change. Downloading with failure handling avoids treating an HTTP error page as a shell script:

curl --fail --location --output almalinux-deploy.sh \
  https://raw.githubusercontent.com/AlmaLinux/almalinux-deploy/master/almalinux-deploy.sh
less almalinux-deploy.sh
bash almalinux-deploy.sh --help

The current requirements include root privileges, sufficient disk space, working repository access and dnf-plugins-core. Install that package through the appropriate functioning repositories if needed. Review help against the downloaded version; do not add Stream downgrade or package-exclusion flags to a CentOS Linux conversion by habit.

Run the conversion in the planned maintenance window

Once compatibility, backups, source preparation and console access are confirmed, the standard documented invocation is:

sudo bash almalinux-deploy.sh

Watch the output and investigate errors. Do not treat a partially completed package operation as success or run unrelated cleanup commands over it. Consult the current tool documentation and retained logs if the process stops.

After a reported successful conversion, reboot in the maintenance window so the host can use its AlmaLinux kernel:

When you convert CentOS 8 to AlmaLinux 8, verify repositories and application behavior as well as the release name.

sudo reboot

Validate the operating system and the application

cat /etc/almalinux-release
uname -r
sudo grubby --info DEFAULT
sudo dnf repolist --enabled
sudo dnf check
systemctl --failed

These checks provide evidence, not a complete acceptance test. Confirm the expected default kernel and boot configuration for the host, review remaining third-party repositories and investigate failed services. A converted container is different: it uses its host’s kernel rather than independently booting one.

Then test real application flows: database reads and writes, websites, authentication, mail, scheduled jobs and any remote integrations. Confirm that monitoring and backups run on the converted system. Keep the original recovery point until the agreed validation period has passed.

Does this upgrade the server to AlmaLinux 9?

No. A CentOS 8 to AlmaLinux 8 conversion stays within the same major version. Moving to another major release needs a separate supported upgrade or a replacement-server plan. For a cPanel server starting on CentOS 7, use the cPanel-specific ELevate guide instead.

The migration is complete when the service is verifiably healthy and maintainable, not merely when a release file changes. Which application test would reveal the most important failure on your own server?

Convert CentOS 8 to AlmaLinux 8: references and related reading

Related reading: Install TypeScript on AlmaLinux: A Practical Project Setup

A practical guide for your next challenge. A fresh perspective for everyday life. Discover both through Nandan’s latest articles.

Post Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

WhatsAppLet's connect