-
Notifications
You must be signed in to change notification settings - Fork 379
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
Consistently use a string type for expectedLayerDiffIDFlag #2603
Conversation
@edsantiago This is a guess at the problem and fix; not reproduced, untested. Filing early just in case it happened to unblock you. |
Sigh, another one I can't reproduce, but with this vendored in I'm seeing a lot of:
(could be completely unrelated; could be that your PR lets things go through a little farther and then something else is breaking. I need to switch gears) |
That’s … not a helpful message from c/image or c/storage. Not too likely to be directly related, but also I don’t have any idea where it is coming from. |
9b1a056
to
6045533
Compare
I have confirmed that this fixes #2602, at least per the custom reproducer in #2602 (comment) ; this is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One thing I don't understand here is what's the other code that is setting this to a Digest type? It doesn't seem to be in c/image or c/storage, but maybe I'm missing it.
@@ -930,7 +930,7 @@ func (s *storageImageDestination) createNewLayer(index int, layerDigest digest.D | |||
|
|||
flags := make(map[string]interface{}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was map[string]interface{}
chosen here? It came in 15ac716f1690cb04f3694e7b295e4830217e8c62 but I don't understand why it couldn't be a structure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See how it is used in that commit; this goes all the way back to 7426cceb6fc121882d601fdfb309e075ecd6f10d .
As for why this does not record specific fields … *shrug* it’s an escape hatch so that out-of-c/storage users can store their private data without properly maintaining a c/storage type extension or without making that data public to all c/storage users; and that’s basically what’s happening here.
Still seeing not supported and blob size mismatch but I guess one bug at a time |
I don’t understand the question. The patched line is the only writer, and |
I don’t immediately know; it’s not happening when just pulling that image from Quay. Looking at https://github.com/containers/podman/blob/740f1d1fc710d4560d2463b11333cc9ad68e22bd/vendor/github.com/containers/storage/pkg/chunked/storage_linux.go#L1156 , that Podman version does not include containers/storage#2130 yet, so that is expected. (I’m currently working with containers/podman#24287 .)
Yes please. |
It's possible that "not supported" is only showing up on |
Hurray for stepping afk! The problem is with VFS. containers/podman#24308 |
go mod edit -replace github.com/containers/image/v5=github.com/mtrmac/image/v5@untrusted-digest-flag Signed-off-by: Miloslav Trmač <[email protected]>
go mod edit -replace github.com/containers/image/v5=github.com/mtrmac/image/v5@untrusted-digest-flag Signed-off-by: Miloslav Trmač <[email protected]>
go mod edit -replace github.com/containers/image/v5=github.com/mtrmac/image/v5@untrusted-digest-flag Signed-off-by: Miloslav Trmač <[email protected]>
6045533
to
5ff751e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Might be a fix for containers#2602 . Signed-off-by: Miloslav Trmač <[email protected]>
5ff751e
to
5e9449c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Might be a fix for #2602 .