Unassociate tags from images in images list view #9473
philippkunz
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
I'm always frustrated when I want to un-associate multiple tags from different images. In the images list view (/#/images) I can filter for tag names that contain a substring and can see those tags in the table immediately filtered but to un-assign the tags and remove the image only when no longer referenced just like "docker image rm someimage:latest" i'd have to click each of those images, click the trash button, go back, search again, and so on.
Proposal
I would prefer a checkbox next to each tag name in the tags column just like in the id column displaying the hash. The "remove"-button above the table would then in addition to its existing behavior un-associate the selected tags and just like "docker image rm" also actually remove the image the tag was associated with if nowhere (container, another image's predecessor, another tag, ...) referenced any longer.
Alternatives
I used bash as an alternative but it's not as nice to use. Few additional clicks would do it as well.
Additional context
There might be similar other tables but I found none that could be enhanced in a similar way.
The suggested new feature would probably not add value for most users but in my opinion also not distract any one or overload the frontend excessively.
The idea for this feature comes from a project where numerous builds produce numerous images each most of which identical but not always handing the result of one build step to another by means of an image tag name following a convention. most docker build steps are served from cached images which is also why it is important to hold many images as cache. at the end of a build some tags are overwritten by assigning the same or a new image to a new or existing tag name and others are removed. if that last cleanup step fails, many many clicks are necessary to get rid again of those temporary tags.
I'm curious to hear what other think even if they find it's not a good idea or how else the problem could be avoided or addressed.
Beta Was this translation helpful? Give feedback.
All reactions