23, Nov 2026 RSS feed ↗

AlmaLinux ELevate Can Now Upgrade From a Local DVD Image

An AlmaLinux server that cannot reach an online repository can now use a local installation DVD image for an in-place major upgrade. The November 20 ELevate Stable release covers AlmaLinux 8 to 9 and 9 to 10. It also makes a separate path available from AlmaLinux 9 to the older-CPU build of AlmaLinux 10. These changes answer two different questions. The DVD changes where packages come from. The CPU build changes which packages the machine can run.

Choose the target build before fetching the image

AlmaLinux 10 normally targets x86-64-v3. The project publishes an x86-64-v2 build for older machines, and ELevate Stable now offers routes to both AlmaLinux 10 and AlmaLinux Kitten 10 in that variant. On a fleet with mixed hardware, record the CPU capabilities of each host or virtual machine before you stage any images. A VM can expose a narrower set of features than its physical host, so do that check inside the guest you intend to upgrade.

The v2 route has its own Leapp data packages and requires a matching root filesystem image as part of preparation. AlmaLinux identifies EPEL as the supported third-party repository on those routes. Check the project’s v2 instructions before starting with a package list from a standard x86-64-v3 upgrade.

Know what the DVD can supply

The local ISO supplies the target distribution’s packages during the upgrade, including the stage that runs after reboot. Install the ELevate tooling before you start. The installation media does not include CodeReady Builder or third-party repositories, so inventory those dependencies and plan how to handle them after the upgrade. The project still documents local mirrors for sites that already maintain a broader offline package collection.

With the target DVD staged on local storage, give its path to both leapp preupgrade and leapp upgrade using the --iso option. Read the preupgrade report before committing to the reboot. In particular, identify any service whose RPM came from outside the distribution and decide how you will restore it if its dependency remains unavailable.

Test a service as well as the reboot

On a test clone, start the workload that drove the original maintenance request. For a container host, that can mean starting the usual rootless service and checking that another machine can reach its published port. The AlmaLinux 10.3 Podman changes show why a successful operating-system boot can still leave decisions about storage and networking for the application owner. Keep a tested snapshot or backup until those service checks pass.

AlmaLinux’s release announcement and ELevate Quickstart Guide describe the supported paths and preparation requirements.

F

Faith Thompson

Faith Thompson approaches online writing through language, culture and the questions readers bring to a page. With a background in English literature at the University of Leeds, she is interested in how a song, a software interface or a company statement can mean different things once its context is explained. Her work across the network ranges from music and lyrics features to accessible technology guides and coverage of changes affecting digital consumers. Faith's preferred format is a clear, carefully paced explanation: establish what is known, unpack the detail that is easy to miss, then show why it matters. She gives particular attention to terminology, source attribution and the practical steps that turn a broad topic into something a reader can use.

More from this author →