portainer: Portainer incorrectly marks used images as unused
Description
In the latest version, Portainer marks images which are in use as unused. You can see in the above screenshot that it failed to delete an image marked as unused because it is in use.
Steps to reproduce the issue:
- Unknown how this was produced. This happens to some but not all of the images in use.
Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Technical details:
- Portainer version: 1.13.3
- Target Docker version (the host/cluster you manage): 17.05.0-ce
- Platform (windows/linux): Linux
- Command used to start Portainer (
docker run -p 9000:9000 portainer/portainer): Docker compose file - Target Swarm version (if applicable): 17.05.0-ce
- Browser: Chrome 59 on Ubuntu
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 15 (8 by maintainers)
Commits related to this issue
- feat(stack): make stack created from app template editable EE-1941 (#1047) feat(stack): make stack created from app template editable EE-1941 (#1047) — committed to portainer/portainer by deleted user 3 years ago
As an addition to this, portainer also marks images used by a hidden container as Unused.
I’m running a lot of containers but don’t want to see the portainer container, so I set it to hidden (in the settings, with a label), but that doesn’t mean the image is unused.
I think that the goal here is to differentiate which image are used by containers and which one are not. I’d rather have a single ‘Unused’ label to avoid cluttering the UI. Maybe the ‘Unused’ tag should not be associated to images that have children tho, even if they are not used by any containers.
@redraw we’re aware of this and should be fixed with the introduction of UAC on images: https://github.com/portainer/portainer/issues/2405