-
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
History in base image is reset when registry uses manifest V2.1 such as Quay #1634
Comments
See #1641, which is closely related. History is low priority though. |
Note that #1644 doesn't fix this at least for the example in #1641. The container config JSON in the For example, with the following Dockerfile, FROM quay.io/tremolosecurity/myvirtualdirectory-base:latest
LABEL something=new
The V2.1 manifest in this case is
So reconstructing proper history from V2.1 requires quite a lot of work. |
So what does this exactly involve? |
To clarify, there's only one version of container config template being used when consuming both V2.1 and V2.2 manifests. By its definition, the container config template defines a For V2.1, the template is matched against the first And seems like to restructure the proper history, we need to go through all
The |
Will not work on V2.1 manifest. |
While investgating #1627, I noticed that history of all the layers in the base image is reset if the registry is returning manifest V.21. Check "auto-generated by Jib" below:
This is because we are not calling
addHistory()
inJsonToImageTranslato.rtoImage(V21ManifestTemplate)
. Low priority because it happens only when the registry is using the old schema and the history is basically informative comments.The text was updated successfully, but these errors were encountered: