You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I push multiple dev images then untagged images will accumulate. The most recently pushed untagged images will correctly point to the dev tag but the others will be orphans. I would like to prune these orphaned and untagged images.
Do you think your action could be extended to support this use case?
Thanks,
Ben
The text was updated successfully, but these errors were encountered:
As it stands, this action supports pruning untagged images. If my understanding is correct, you only want to prune images that are both untagged and orphaned, where "orphaned" means the image SHA digest is not used as a reference in a separate multi-arch image manifest. Is that right?
If it is, then this seems like this would require introspection of image manifests to compile a list of SHAs that are not orphans and should not be pruned. This is beyond the present scope of this action which is purely driven by GitHub's API and remains quite simplistic on purpose to avoid unexpected behaviours. Also, I'm not sure this use case is generic enough to have a place here.
However, if you do want to have a go at it, feel free to fork this action as a starting point.
Hello,
Thanks for making this great action 😄
I have a package with multi-architecture images. Each tag points to an untagged image for each architecture, like:
If I push multiple dev images then untagged images will accumulate. The most recently pushed untagged images will correctly point to the dev tag but the others will be orphans. I would like to prune these orphaned and untagged images.
Do you think your action could be extended to support this use case?
Thanks,
Ben
The text was updated successfully, but these errors were encountered: