Bug 2038126

Summary:	Backward compatibility of podman-compose
Product:	[Fedora] Fedora	Reporter:	Lumír Balhar <lbalhar>
Component:	podman-compose	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	35	CC:	gwync, kdudka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	podman-compose-1.0.3-2.fc34 podman-compose-1.0.3-2.fc35	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-16 00:57:50 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 Lumír Balhar 2022-01-07 11:09:20 UTC

I see that there has been a big update of podman-compose from 0.1.8 to 1.0.3 in Fedora 35. If I correctly understand this note[0] the new version does not support DNS name resolution between the containers out of the box and needs a dnsname plugin for that.

Would it make sense to make podman-compose in Fedora 35 and 34 require podman-plugins package where this plugin is available to preserve the functionality and prevent the update from breaking backward compatibility in already released distributions?

[0] https://github.com/containers/podman-compose/blob/devel/README.md#podman-compose

Comment 1 Gwyn Ciesla 2022-01-07 16:06:23 UTC

Absolutely, I'll get an update out.

Comment 2 Fedora Update System 2022-01-07 16:18:43 UTC

FEDORA-2022-7e551c2d7d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7e551c2d7d

Comment 3 Fedora Update System 2022-01-07 16:18:44 UTC

FEDORA-2022-ea0ecd7773 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ea0ecd7773

Comment 4 Fedora Update System 2022-01-08 01:09:41 UTC

FEDORA-2022-7e551c2d7d has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-7e551c2d7d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7e551c2d7d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-01-08 01:41:22 UTC

FEDORA-2022-ea0ecd7773 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-ea0ecd7773`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ea0ecd7773

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-01-16 00:57:50 UTC

FEDORA-2022-7e551c2d7d has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2022-01-16 01:18:13 UTC

FEDORA-2022-ea0ecd7773 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.