Upgrade to 10.5 on unsupported OS (CentOs 7)

I’m running latest Axigen 10.3 on CentOs 7 and would like upgrade to 10.5.
There is no support of 10.5 on CentOs 7 formally and live (I tried to install RPM of 10.5 and received some failed dependencies error about libc and libstdc++), so I should make something harder that just download new version, start it and wait for migration procedures will finish.
Are there any tested options for doing this?

After a small research I see 2 main options:

  1. Start using latest version of 10.5 through docker image on the same old server.
    But here is question how can I import all messages database and configuration to this new version of Axigen.
    As far as I understand, the usual option for upgrading from 10.3 to 10.5 is to upgrade to 10.5 by running the installer in the RPM/DEB package, during which the storage will be migrated, including the creation of new indexes and other little things that should not be done manually. And I cannot do “upgrade” in this case because it will be fresh installation in docker container.
    Is there any manual or just steps guide how can I transfer configs and storage from 10.3 to another fresh installed instrance of Axigen (10.5)? Or maybe docker image of 10.3 exists and I can install 10.3 in docker container, move configs and data folder to mounted docker volume and upgrade 10.3 in container to 10.5?

  2. Install Axigen on fresh server with supported OS (CentOs 9 or, for example, Ubuntu 22.04) and transfer all configs and data folder to this server.
    In this case I think better to try install 10.3 on new server, after that move configs and data folder from old server, start axigen and chek all works correct, and after that start upgrade routine to 10.5?

Which of these methods is preferable? Or maybe there is some other option that I’m overlooking?

Hello,

You can do an in-place upgrade to Rocky 8 like this:

I had to add this before running leapp upgrade

export LEAPP_OVL_SIZE=4096

You can then run the 10.5 installer

Hello,
I am facing the same problem. I think that option 2 is the one that best suits for my case. Have you found a solution?