Bug 2120220

Summary: Need latest version of podman-compose in RHEL8 EPEL
Product: [Fedora] Fedora EPEL Reporter: Ketan Bhandari <bhandari.ketan02>
Component: podman-composeAssignee: Gwyn Ciesla <gwync>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: bbaude, dwalsh, gwync, jligon, jnovy, jwboyer, lsm5, mheon, pthomas, umohnani
Target Milestone: ---Flags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-22 14:17:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ketan Bhandari 2022-08-22 08:45:02 UTC
Description of problem:
Currently in rhel8 epel we have podman-compose version 0.1.7dev. We are facing some issue with this version. Podman team recommended to use newer version 1.x
Could you please upgrade the version in epel? Thank you!!

Reference - https://github.com/containers/podman-compose/issues/539

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
podman-compose -f <compose.yml> up

Actual results:
Container should be up and running. Same yml working fine with podman version 4.0.2

Expected results:
Getting error
Error: invalid config provided: extra host entries must be specified on the pod: network cannot be configured when it is shared with a pod
125

Additional info:
Version
using podman version: podman version 4.1.1
podman-composer version 0.1.7dev
podman --version
podman version 4.1.1

yml

I have added the extra_hosts in compose but no luck.
extra_hosts:
- "host:IP"
If i run directly using podman by adding --add-host, it works

Comment 1 Gwyn Ciesla 2022-08-22 14:17:45 UTC

*** This bug has been marked as a duplicate of bug 2094882 ***