Feature: Are there any plans to support other container registries (not just GHCR)?

[ruzickap]

ghcr-cleanup-action brings a great functionality for cleaning up the GitHub GHCR.

Are there any plans to extend it to quay.io, Docker Hub, Amazon ECR, Harbor, ... ?

Thank you...

[rohanmars]

I'm glad it's useful to you @ruzickap. Initially, I ruled it out when I saw how GitHub handles packages, it's a very specific API and the action makes these vendor specific API calls. Which is why I named the action with a "ghcr" in it. I did have that question to myself right at the beginning.

However, after implementing this action and especially the referrers/sigstore logic, it probably makes sense to implement a generic registry cleanup action. It would probably be easier to implement a new action for generic registry support (registry-cleanup-action) rather than make this action support generic registries. But I need to investigate that further.

I've noticed githlab and the docker "distribution" handle multi-architecture images internally without any additional steps; however, they don't handle referrers/attestation images.

I probably need to review the different registries and figure out what can be implemented from just the registry API, how they handle multi-architecture cleanup, and if they have an internal API for their registry.

Do you have the specific need for any of the above registries currently?

[ruzickap]

That sounds like a complete rewrite of the current GitHub Action.

Actually, I was looking for something more "generic" that can be used to clean multiple container registries. Unfortunately, I failed to find anything except this GitHub action specifically designed for the GitHub Container Registry (GHCR).

While I use Quay.io and Docker Hub, it might be challenging to cover all the popular container registries.
Nevertheless, it's an interesting idea...

[rohanmars]

Some of the code from this action could be lifted (now that I understand the mechanisms of image cleanup better), so maybe it's not a complete rewrite. My gut feeling is an action could be written to just operate on the registry API itself. So it would likely work across the registries that support the DELETE method on the manifest/image (github cr doesn't).

Let me investigate more. I have a few technical questions I need to answer.