Thanks for the info. In terms of a possible quick solution, I wonder if there is a non-intrusive fix that can be identified and easily backported to podman 1.5 to solve your issue. Or if @andrunko can think of any other low-effort solutions to make this work.
Otherwise, to be honest, it’ll probably be a few months before we upgrade, I apologise for any inconvenience. The situation is that we have our distro based on Debian, but the podman packages weren’t in Debian until recently, so we got them from elsewhere, and that makes maintenance a bit painful.
Now podman is officially included in Debian, we should switch to that version instead, but… our whole distro maintenance process is quite manual, and Debian has packaged every single go module as an individual source package, so that equates to a bunch of awkward work.
What we’re working on instead is becoming directly aligned with Debian so that we don’t have our own entire separate distro, at which point adopting Debian’s podman package and dependencies becomes something trivial and automatic. We’re also working on opening up our tools, infrastructure and communication to increase transparency with partners and enable more community involvement. These transitions are taking some time but should bring many rewards going forward.