-
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
Support manifest list specified by digest #1360
Comments
Hi @dzwicker , thanks for reporting this! Jib should be able to support using digests in addition to tags, so this seems like it is not working as intended. |
So it seems that this is happening because you are using explicitly the digest for a manifest list for |
Using the digest for a specific manifest will resolve the issue. However, I see |
The Docker Registry was changed such that if a client requests a tag that maps to a manifest-list but they don't support manifest-lists, then it returns a manifest corresponding to the Unfortunately if you use the docker CLI to pull a something that has a manifest list, docker reports the digest of the manifest-list:
|
So this issue should be fixed by #1811. Going to close for now, expect it to work with the 1.4.0 release |
@dzwicker v1.4.0 has been released with manifest list support! |
@dzwicker it's limited support, but should work for your case (it will pick the amd64/linux base image from a manifest list automatically) |
Description of the issue:
As docker tags can be reference different container digest over time we want to use a digest for the base image.
Expected behavior:
Downloading the base image and build the new application image.
Steps to reproduce:
gradle jib
Environment:
jib-gradle-plugin
Configuration:Additional info:
The problem is that the docker registry returns an unknown mediatype for the mainfest. It is
application/vnd.docker.distribution.manifest.list.v2+json
. Thelist
is the problem as it is unknown by theManifestPuller
.Log output:
The text was updated successfully, but these errors were encountered: