-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Jib should report the base image digest that is used #1884
Comments
Hi! Can I take this up? |
Sure, thanks! |
Presumably we could just read the Alternatively we could compute the SHA on the fly inside However, @jonjohnsonjr sent us some links and said to proceed with caution with the header approach, as registries have implemented this so differently. Generally it's questionable to trust the header value.
|
So @chanseokoh I shall work on getting the manifest from the registry first. This should resolve #2034 as well. |
@chanseokoh There is one problem with computing the digest from the response directly. Manifest has signatures. We compute the digest from the manifest without the signatures. And you had suggested to compute the digest directly from the inputStream. |
Only schema 1 images have signatures, which jib doesn't support (I believe). |
@jonjohnsonjr Jib doesn't support pushing schema 1 images, but it supports pulling schema 1 base images. @tejaskasetty I think we can ignore schema 1 manifests. They will be gone sooner or later. We are checking if the schema is 1 or 2 in |
Fixed by #2063. |
@dev-gaur We've released 1.7.0 with @tejaskasetty's fix! |
Jib should report the image digest used for the base image to simplify configuring a fixed digest, and also for traceability.
The text was updated successfully, but these errors were encountered: