docker / hub-feedback

Feedback and bug reports for the Docker Hub
https://hub.docker.com
233 stars 40 forks source link

Advanced Image Management Feedback #2175

Open mbentley opened 2 years ago

mbentley commented 2 years ago

Problem description

The Advanced Image Management user experience needs some work as there are some odd behaviors.

  1. Try to go to the Advanced Image Management of a repository that does not have inactive images. What if I actually want to remove an untagged image that Docker Hub calls "Active"? There isn't a way to do so unless you go to the advanced image management URL manually.
  2. I have a repository with over 1000 inactive image digests (see https://hub.docker.com/usage/docker/mbentley?repo=omada-controller). I would have to go through 40 some pages of images to delete them. There doesn't appear to be a way to prune all of them as it will only select one page at a time.
  3. If I delete all of the images from the last page, the interface isn't smart enough to take me to the last page. It just reports that there are not any results for the page that I just deleted. There is no navigation to go back to the first page. I have to remove the page number from the URI to go back to the first page.

Screen shots for all of the above are below.

docker info output

n/a

Debug Information

Browser name and version: Google Chrome 95.0.4638.69 (Official Build) (arm64) URL: https://hub.docker.com/usage/docker/mbentley?repo=omada-controller Timetamp or time range: n/a Public IP: 104.254.222.95 Hub Username: mbentley

Error messages (on screen or in browser console)

n/a

Screenshots of the issue (if applicable)

For item 1 above - No way to navigate through the UI to always see advanced image management:

screenshot 2021-11-18 at 7 47 43 AM

For item 2 above - There is no way to select all images on all pages:

screenshot 2021-11-18 at 7 48 53 AM

For item 3 above - Deleting images on last page takes me back here:

screenshot 2021-11-18 at 7 38 22 AM

Task List

ingshtrom commented 2 years ago

👋 @mbentley

Thanks for the feedback! These have been forwarded to the team. I cannot give a timeline on fixing it, but we will follow up with any further questions we have.