-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Digest could be invalid when using multiple registries #15652
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
/cc @dhaus67 |
janisz
referenced
this issue
Sep 6, 2022
Generate an image's RepoDigests list using all applicable digests, and refrain from outputting a digest in the tag column of the "images" output. Signed-off-by: Nalin Dahyabhai <[email protected]>
@mtrmac @vrothberg @nalind PTAL |
@mtrmac can we close this as a duplicate? |
Let’s. (I don’t have a strong opinion on which one to close — keeping the full context of #3761 seems valuable, OTOH this one is a concise description of a specific problem, without the debugging session, and without other people piling on with not-exactly-the-same issues.) |
Closing as a duplicate of #3761. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
Description
Reported RepoDigests are invalid when pulling image from more than one registry.
podman does cross product of image names and all available digests which can lead to invalid repo digests as digest is registry specific.
Similar to: cri-o/cri-o#6208
Steps to reproduce the issue:
Pull the same image from two registries
Inspect images and their repo digests
Describe the results you received:
Describe the results you expected:
Docker output
The text was updated successfully, but these errors were encountered: