Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#74101 - [podman-compose] Consider adding podman-dnsname as dependency

Attached to Project: Community Packages
Opened by Spout (sutupud) - Saturday, 12 March 2022, 12:57 GMT
Last edited by David Runge (dvzrv) - Friday, 06 May 2022, 18:31 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Filipe LaĆ­ns (FFY00)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



It seems that when the podman-dnsname package is not installed, services defined in a compose file can't discover each other by service name.
When that package is installed, the plugin will be used by newly created networks automatically to provide service discovery, which when migrating from docker-compose is basically what would be expected to work out of the box, without it functionality is drastically limited.

At the very least it should be set as an optional dependency.

Additional info:
* package version(s): podman-compose 1.0.3-1
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 06 May 2022, 18:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed with podman-compose 1.0.3-2
Comment by David Runge (dvzrv) - Friday, 06 May 2022, 18:29 GMT
@sutupud: Thanks for the ticket.

I"ll add it in a pkgrel bump.