After updating a container and entering the image tab, there is often a double entry from an image. I understand that when several services using one image and not every service is updated, it can occur, but in this particular case only one service uses this image.
It's just an example, because it happens with different images.
My guess looking at the compose settings and a quick look at the source code (here) is that what you see is the result of caching. It makes viewing stuff smoother but obviously can have side effects. You could try to reduce caching time in the settings to 0 and try again. Default is only 60 seconds so you probably were very quick with what you did.
It's just an example, because it happens with different images.
What is the output of (this is the command the plugin uses to enumerate images):
sudo docker image ls --all --digests --no-trunc
My guess looking at the compose settings and a quick look at the source code (here) is that what you see is the result of caching. It makes viewing stuff smoother but obviously can have side effects. You could try to reduce caching time in the settings to 0 and try again. Default is only 60 seconds so you probably were very quick with what you did.
The cache is all or nothing cache. It doesn't add or remove images. It rewrites it completely every time it refreshes. No need to change the cache time. Just click the Clear Cache button on the Settings tab.
What is the output of (this is the command the plugin uses to enumerate images):
sudo docker image ls --all --digests --no-trunc
mongo latest sha256:15fb53a5160ebabff5ecade8f8b5d48721b68ea190957a7f35b5b38e8340e62b sha256:14bce8bf75c7ffb890108dea16aae00d9f1667b86f19494515e347b0ff3d6dc9 2 weeks ago 892MB
mongo latest sha256:98028cf281bb5d49ace5e1ddbd4509e8f1382fe80ef1cf101eeefdc106d76cd4 sha256:14bce8bf75c7ffb890108dea16aae00d9f1667b86f19494515e347b0ff3d6dc9 2 weeks ago 892MB
This is why you see two of the "same" image. There can be more than one image with the same tag with different digests. If you make the id or digest column visible, you would see that they are different.
Thanks for the explanation and now makes sense to me why this only ever happens with one image (mongo) on my system.
Good to know I can ignore it
Are there actually two images being stored but only one being used?
Is there anything that can be done fix this?
Are there actually two images being stored but only one being used?
Kind of. Both are likely being used (or were at one point) but they likely share most or all of the image layers. So, it is doubtful that it takes up any additional space.
Is there anything that can be done fix this?
The problem is that what it is displaying is correct. People who have this situation likely have two or more containers using the same image. But container 1 is using image:latest with digest 1 and container 2 is using image:latest with digest 2. If I don't use the digests of the image and compare with the digest of the containers, it might show an image as not in use when it is in use. I guess I can look at a way to store all of the digests for image:tag to deduplicate and show multiple digests/ids in the columns.
Is there anything that can be done fix this?
I'm actually happy with this change - https://github.com/OpenMediaVa…ef878dcff6e8fca9a9fe78197
Nice one and thanks. I will let you know if it resolves the issue I have with mongo.
I only have one container using mongo (UniFi) but do see this issue with the duplicate image. Both are marked as in use
7.6.8 is in the repo
thanks ryecoaaron - I now have only one image in the image list but it is the one that is shows as 'available' - so not showing as 'current'
I can confirm that the image is current just not displaying correctly in the status field.
I should have been clearer that in my case that the two duplicate images had different 'status' - so apologies for this
I now have only one image in the image list but it is the one that is shows as 'available' - so not showing as 'current'
I can confirm that the image is current just not displaying correctly in the status field.
I should have been clearer that in my case that the two duplicate images had different 'status' - so apologies for this
On my main compose instance, I have three container images that were doubled. So, I have a good test system and understand the issue.
Since the code is deduplicating the multiple digests that one image:tag has, it has to pick one digest to check if there is a new image available. The code compares the digest passed with the digest of the latest image:tag. If they are same, it says the image is current otherwise available. Unless I show multiple status for each digest, it is hard to know which is the "right" one. I will look at it again but...
All good and thanks as always for the amazing work you do for this project. Let me know if I can do anything to help test etc.
7.6.9 is in the repo. For each image:tag, the plugin checks all digests and if any digest is current, the image status will be current.
confirmed now working correctly. thanks again.
Don’t have an account yet? Register yourself now and be a part of our community!
