Reflect podman 5.4 support in ECE doc #3748
Conversation
Reflect podman 5.4 support in ECE doc
kunisen
added
the
supportability
|
|
||
| ```sh | ||
| sudo dnf install podman-5.2.2 podman-remote-5.2.2 | ||
| sudo dnf install podman-5.4.* podman-remote-5.4.* |
There was a problem hiding this comment.
is it correct technically to specify the dnf command install like this?
There was a problem hiding this comment.
yes, dnf supports wildcards and I did a quick test on rocky9 to confirm:
sh-5.1# dnf install podman-5.4.* podman-remote-5.4.*
Rocky Linux 9 - BaseOS 2.4 MB/s | 2.5 MB 00:01
Rocky Linux 9 - AppStream 8.1 MB/s | 9.5 MB 00:01
Rocky Linux 9 - Extras 43 kB/s | 17 kB 00:00
Dependencies resolved.
======================================================================================================================================================================================================================================================================================================================================================
Package Architecture Version Repository Size
======================================================================================================================================================================================================================================================================================================================================================
Installing:
podman x86_64 5:5.4.0-13.el9_6 appstream 17 M
podman-remote x86_64 5:5.4.0-13.el9_6 appstream 11 M
Installing dependencies:
There was a problem hiding this comment.
Hi folks, as you also noticed the discussion with Matt, we could use a wilder scope of 5.x here to install the podman 5 latest version. As of writing, 5.4, result is the same, but the new command is more aligned to what we support.
Details in below comment:
#3748 (comment)
[1]@Kushmaro yes, I did a test for this, as described in my initial post.
Next time I will post my steps in doc PR directly maybe that could have better visibility :) [2]I was also thinking of whether we should add some more notes regarding the version lock. Thinking on this and adding a note as addendum would make the doc and our users/customers have less confusion in the future when upgrading their podman. I will merge this doc PR once we have this context piece confirmed and reflected. |
|
Thank you all! [1]@matt-elastic I reflected what we have synced internally (link). [2]@matt-elastic, @Kushmaro, @jakommo, (cc @shainaraskas), for the record, this is the test log I did for (A) installing podman 5.x and podman-remote 5.x, where x is the latest version (currently it's 5.4), and (B) version lock on major version like what we have for podman 4.x, but not to version lock on minor version, like what we did so far, e.g. podman version 5.4.x. :: (A) Install podman 5.x and podman-remote 5.x where x is the latest version $ sudo dnf install podman-5.* podman-remote-5.*
Last metadata expiration check: 0:02:55 ago on Thu 06 Nov 2025 04:39:57 AM UTC.
Dependencies resolved.
===============================================================================================================================================================================
Package Architecture Version Repository Size
===============================================================================================================================================================================
Installing:
podman x86_64 5:5.4.0-13.el9_6 rhui-rhel-9-for-x86_64-appstream-rhui-rpms 17 M
podman-remote x86_64 5:5.4.0-13.el9_6 rhui-rhel-9-for-x86_64-appstream-rhui-rpms 11 M
(... skip ...)
Installed size: 117 M
Is this ok [y/N]: y
(... skip ...)
Installed:
aardvark-dns-2:1.14.0-1.el9.x86_64 conmon-3:2.1.12-1.el9.x86_64 container-selinux-4:2.237.0-2.el9_6.noarch containers-common-2:1-117.el9_6.x86_64
criu-3.19-1.2.el9_6.x86_64 criu-libs-3.19-1.2.el9_6.x86_64 crun-1.23.1-2.el9_6.x86_64 fuse-common-3.10.2-9.el9.x86_64
fuse-overlayfs-1.14-1.el9.x86_64 fuse3-3.10.2-9.el9.x86_64 fuse3-libs-3.10.2-9.el9.x86_64 libnet-1.2-7.el9.x86_64
libslirp-4.4.0-8.el9.x86_64 netavark-2:1.14.1-1.el9_6.x86_64 passt-0^20250217.ga1e48a0-13.el9_6.x86_64 passt-selinux-0^20250217.ga1e48a0-13.el9_6.noarch
podman-5:5.4.0-13.el9_6.x86_64 podman-remote-5:5.4.0-13.el9_6.x86_64 protobuf-c-1.3.3-13.el9.x86_64 shadow-utils-subid-2:4.9-12.el9.x86_64
slirp4netns-1.3.2-1.el9.x86_64 yajl-2.1.0-25.el9.x86_64
Complete!:: (B) Version lock against major version but not minor version (Updated after chatting with Matt) # sudo dnf versionlock add --raw 'podman-5.*'
sudo dnf versionlock add --raw 'podman-remote-5.*'
Last metadata expiration check: 1:45:45 ago on Thu 06 Nov 2025 12:14:03 PM UTC.
Adding versionlock on: podman-5.*
Last metadata expiration check: 1:45:48 ago on Thu 06 Nov 2025 12:14:03 PM UTC.
Adding versionlock on: podman-remote-5.*
# sudo dnf versionlock list
Last metadata expiration check: 1:46:52 ago on Thu 06 Nov 2025 12:14:03 PM UTC.
podman-5.*
podman-remote-5.*FYI, you can check here (cf: link) for more details about version lock, and installation related test. |
|
Thank you @matt-elastic for the sync! I updated the original ticket here to record the test log we did 2nd time (I will also append what we have chatted about version lock test later also) |
|
Thanks Matt and Shaina! @shainaraskas we are good to merge.
Yes, this applies to ECE 4 as well. (RHEL 9 / Rocky 9 + Podman 5, is supported on ECE 3.8 and 4) FWIW, we are also updating our support matrix internally (link) at the same time (website ticket). Please feel free to let us know if anything is unclear or missing. Thanks again! |
Issue
This issue is to update public doc to reflect podman 5.4 support.
Internal link
Podman 5.4 installation test log
This is to double check installation command for podman and podman-remote 5.4.
Internal link
Confirmation: Podman 5.4 vs Podman 5.*
Checking internally do we support podman 5.4 or we could support an expanded scope of podman 5.*. Depending on @matt-elastic or @Kushmaro's answer, the content in this PR may change.
Internal link
Related: Website page update
We also need to update support matrix to reflect this. Working with the relevant stakeholders.
Internal link
Preview before PR merge
Preview after PR merge
cc @jakommo @pfcoperez @gigerdo