Any way to include old (8.5) packages on new rocky (8.6) server

Hello all!

I need to run podman 3.4.2 and therefor can not upgrade to Rocky 8.6.
Is there any way to include some 8.5 packages on my 8.6 server ?
It seems to be possible to install podman-3.4.2 on a RHEL8 server.

/Peter

Well, there are modules, but the closest you will get is 3.0.x version,so:

[root@rocky8 ~]# dnf module enable container-tools:3.0
Last metadata expiration check: 1:44:25 ago on Thu 15 Sep 2022 14:34:02 CEST.
Dependencies resolved.
====================================================================================================
 Package                Architecture          Version                  Repository              Size
====================================================================================================
Enabling module streams:
 container-tools                              3.0                                                  

Transaction Summary
====================================================================================================

Is this ok [y/N]: y
Complete!

[root@rocky8 ~]# dnf info podman
Last metadata expiration check: 1:44:32 ago on Thu 15 Sep 2022 14:34:02 CEST.
Available Packages
Name         : podman
Version      : 3.0.1
Release      : 9.module+el8.6.0+973+7a06b91e
Architecture : x86_64
Size         : 11 M
Source       : podman-3.0.1-9.module+el8.6.0+973+7a06b91e.src.rpm
Repository   : appstream
Summary      : Manage Pods, Containers and Container Images
URL          : https://podman.io/
License      : ASL 2.0 and GPLv3+
Description  : podman (Pod Manager) is a fully featured container engine that is a simple
             : daemonless tool.  podman provides a Docker-CLI comparable command line that
             : eases the transition from other container engines and allows the management of
             : pods, containers and images.  Simply put: alias docker=podman.
             : Most podman commands can be run as a regular user, without requiring
             : additional privileges.
             : 
             : podman uses Buildah(1) internally to create container images.
             : Both tools share image (not container) storage, hence each can use or
             : manipulate images (but not containers) created by the other.
             : 
             : Manage Pods, Containers and Container Images
             : podman Simple management tool for pods, containers and images

another alternative would be install the Rocky 8.5, change the repo files in /etc/yum.repos.d to use the vault URL for appstream, and see if that will give you podman-3.4.x. Otherwise any yum/dnf will pull 8.6 packages. URL for vault: Index of /vault/rocky/8.5/

yum search podman --showduplicates | egrep ‘^podman’

podman-1.0.0-2.git921f98f.module+el8.0.0+2958+4e823551.x86_64 : Manage Pods, Containers and Container Images
podman-1.0.5-1.gitf604175.module+el8.0.0+4017+bbba319f.x86_64 : Manage Pods, Containers and Container Images
podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64 : Manage Pods, Containers and Container Images

podman-3.3.1-9.module+el8.5.0+12697+018f24d7.x86_64 : Manage Pods, Containers and Container Images
podman-1:3.4.2-9.module+el8.5.0+13852+150547f7.x86_64 : Manage Pods, Containers and Container Images
podman-2:4.0.2-6.module+el8.6.0+14877+f643d2d6.x86_64 : Manage Pods, Containers and Container Images

So on a RHEL8.6 i only need to do ‘yum install podman-3.4.2’
It is a big difference and way easier.

Yes, and the reason why is because RHEL allows pinning to a specific version - and that also allows you to install the version you wanted.

With CentOS, Rocky, Alma or any other derivatives there isn’t any version pinning, and thus that means you cannot do it like you can with RHEL. There is always only the latest version so 8.6 or whatever. That means when 8.7 released, 8.6 will disappear and be moved to the vault. Otherwise, switch repos to 8.5 like I mentioned and you should get podman-3.4.2.

1 Like

But not to every version. RHEL 8.5 is already dead too. The RHEL 8.4 and 8.6 do have EUS. See Red Hat Enterprise Linux Life Cycle - Red Hat Customer Portal

1 Like