[RFC] CentOS, Rocky, Alma 10

Peter pjcreath+proxmox at gmail.com
Wed Sep 10 22:04:43 CEST 2025


After seeing the thread on Debian 13.1, I wanted to ask what the process is
for adding container support for version 10 of the various RHEL families?

As to the mechanics, similar to Trixie, there's a version check that blocks
installing a container running el10:

--- LXC/Setup/CentOS.pm.orig 2025-09-10 15:57:05.961409961 -0400

+++ LXC/Setup/CentOS.pm 2025-09-06 16:22:18.589570360 -0400

@@ -23,5 +23,5 @@



     if (($release =~ m/release\s+(\d+\.\d+)(\.\d+)?/) || ($release =~
m/release\s+(\d+)/)) {

-        if ($1 >= 5 && $1 < 10) {

+        if ($1 >= 5 && $1 < 11) {

             $version = $1;

         }

That lets me install version 10, but then I get a warning each time the
container starts.  It turns out the pattern matching for systemd version is
a little too strict in LXC/Setup/Base.pm:get_systemd_version:

            if ($line =~
/libsystemd-shared-(\d+)(?:[-.][a-zA-Z0-9]+)*\.so:?$/) {

This worked fine for version 9 and earlier, as their .so line looked like
"libsystemd-shared-256.so".  But as of version 10, the .so line is now "
libsystemd-shared-257-9.0.1.el10_0.1.so".  The "el10_0" throws off the
regular expression.

Would it be preferable to loosen the pattern in Base.pm or to copy
get_systemd_version into CentOS.pm and revise the pattern there?


More information about the pve-devel mailing list