The web interface for the Container Images allows for removing entire "repositories" of images (for example, ibmcom/curl-amd64) but not individual tags. Currently the only way to do this on ICP is manually through the Docker Registry v2 API, and the operations require specific access tokens and metadata about the tags the user wants to remove.
Customers that push daily builds with different tags each time will quickly clutter up the tags list given when looking at the image in the web interface. Additionally, if the pushed tags do not correctly re-use previous image layers, then they may run out of disk space in the backing storage for the registry. Being able to remove individual tags more easily would help in this case.
Real Scenario + Problem Statement
|Who would benefit from this IDEA?||As a customer, I want to be able to remove specific images from the private registry so that I can manage the total disk usage.|
Why is it useful?
|Market Evidence - # of customers in next 12 months|
|Avg Annual Contract Value Per Customer|
|Secondary Persona (multi-select)|
How should it work?
|Geo Availability for this IDEA|
|Geo - Use for OBDR Reporting only|