-
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
Add option to tag child images when publishing multi platform #3518
Comments
Would it be possible here:
to optionally change the ternary else from a manifestDigest to val platforImageTags = if (platformTagingEnabled) {
tags.map{
it + "currentPlatformHere"
}
}else{
listOf(manifestDigest.toString())
} where currentPlatformHere is the archname(or os-archname)? |
A prototype. I hardcoded the feature flag on. |
Thanks for filing the feature request and the contribution @robert-csdisco! We will take a look at it. |
I started wiring up the boolean through buildContext, but it looks like there's quite a few places to add it. Will wait to see if this is something y'all could accept before doing the config part |
@mpeddada1 I was a bout to open a PR to fix this, but I see that this issue is not labelled "Accepting Contributions". Is there a reason for that? |
@msvticket I was the original author here on an old work account. I can't add the label, but I would love having it done. :) |
Environment:
-Linux
Description of the issue:
When one uses the platforms section to upload multi-arch images, you end up with untagged images in ECR(probably others too)
Stack overflow version of the same issue with docker buildx here.
When you look in ECR, you see the 2 child images as well as the manifest file.
Expected behavior:
It would be nice if the child images had an option to append a -ARCH to the tag used as the Manifest one. In the above example, it would be awesome if there was an option to tag them with
0.0.130-userAdd -- Manifest
0.0.130-userAdd-amd64 -- AMD version
0.0.130-userAdd-arm64 -- ARM version
The jib section's from block
The text was updated successfully, but these errors were encountered: