Skopeo Tag v1.16.0 Manifest errors on pull-through with podman

[CubexsOne]

In our project environment, we use a harbour registry with a pull-through mirror function to clone images to us accordingly.

Now we are in the process of updating our dependencies and one of them is Skopeo.

If we pull the image with docker from a Macbook with --platform linux/amd64 it works perfectly.

If we do this with podman on a Linux machine, we get an error message that something is not found.

According to the operator of our registry it seems to be a problem in the manifest from the original repo.

Image: skopeo/stable:v1.16.0

For further questions, please write.
I am happy about any help

Best regards
CubexsOne

[mtrmac]

Thanks for reaching out.

I think this needs to be diagnosed server-side, on whatever the blanked-out server is. “not found: repo quay/skopeo/stable, tag not found” (including the double-space after “tag”, suggesting maybe an empty tag) is a text returned by the server.

The skopeo images are re-generated daily ( compare https://quay.io/repository/skopeo/stable?tab=history ), so it’s possible that the mirror / pull-through state got out of sync, maybe removing a per-arch component and not updating the top level yet, or keeping the top level and trying to pull through to an already-removed image, or something like that.

See also https://github.com/containers/image_build/blob/main/README.md about the moving tags.

---

Note to self: The server seems to be Harbor, compare goharbor/harbor#20764 and containers/image#2203 .

[CubexsOne]

Thanks for the answer, I will try to work on this with the admins of the registry.

[mtrmac]

FWIW, for these changing images, you might want to capture

• skopeo inspect --raw docker://…:v1.16.0 | sha256sum to identify the image
• skopeo inspect --raw docker://…:v1.16.0 | jq . or something like that to identify the per-arch references being used
• Correlate the per-arch references from the above with the reading manifest sha256:… messages.

[CubexsOne]

Hii,

FYI: The image 1.16.1 is working.
No one knows why this is working, but I guess its not a problem on your side.

Thanks for helping, have a great time.

[mtrmac]

Thanks for the update.