This fix is already in the upstream sources since the same problem
affected 'podman save' and 'podman load'.
Details
- Reviewers
osa - Group Reviewers
releng - Commits
- R11:588504901fbf: sysutils/skopeo: fix problems with 'skopeo copy' in v1.16.1
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
My understanding is every podman release has multiple components, and here's the quote for v5.2.5:
Updated Buildah to v1.37.5 Updated the containers/storage library to v1.55.1
It seems like that versions of those components are need to be in sync.
@dfr please correct my if I'm wrong.
Also, I've tried to upgrade podman and components to the recent versions, but I've got an issue with the recent version of podman v.5.3.1, so decision was made to upgrade to the more or less "working" version.
Here's another example: the Misc section of the podman-v5.3.0 release notes:
Podman now requires Golang 1.22 or higher to build. ... Updated Buildah to v1.38.0 Updated the containers/common library to v0.61.0 Updated the containers/storage library to v1.56.0 Updated the containers/image library to v5.33.0
I don't think the coupling between the various components is super critical but I think upstream's CI does test that Podman, Buildah and Skopeo work together properly.
I would like to be able to move forward to Podman v5.3 and I have a fairly good idea of how to fix it - I'll work on that next week and make a pull request to fix it in upstream - we can then incorporate the fix into our port.