Skip to content

Commit

Permalink
Use podman from podman-next
Browse files Browse the repository at this point in the history
Enforce podman update to podman next via allow_vendor_change,
allowerasing and best options

Signed-off-by: Nicola Sella <nsella@redhat.com>
  • Loading branch information
inknos committed Feb 27, 2025
1 parent 3556188 commit 0cd044e
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion plans/main.fmf
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,18 @@ prepare:
how: install
package:
- make
- podman
- python3-pip

# tmt copr module seems not enough to install podman from podman-next. I suspect this is related
# to dnf5 vendor stickiness so we need to enforce an update with both allow_vendor_change and
# allowerasing. Best is also needed to ensure the latest version is installed.
- name: enable rhcontainerbot/podman-next update podman
how: shell
script:
- sudo dnf copr enable -y rhcontainerbot/podman-next
- sudo dnf install -y podman
- sudo dnf update -y podman --refresh --setopt=allow_vendor_change=true --best --allowerasing

- name: pip dependencies
how: shell
script:
Expand Down

0 comments on commit 0cd044e

Please sign in to comment.