Which of these container images can I delete - how do I find out?

Hello all

This is ElectricEel-24.10.1, found by looking at apps|configuration|manage container images

(1) How do find these images in the dataset or in the directory structure?

(2) I know that I am currently running (e.g.) adguard/adguardhome:v0.107.55 and I can see listed an earlier version, v0.107.54, which I presume I can delete on the page shown.

However - might there be interdependencies between what I deem to be unused (older, presumably safe to delete) images and those currently running? Here’s what the shot shows me, with my comments after the hyphen on each line:

adguard/adguardhome:v0.107.55	67.98 MiB - currently running	
adguard/adguardhome:v0.107.54	67.86 MiB - older	(safe to delete?)

ghcr.io/tailscale/tailscale:v1.78.3	86.56 MiB - currently running	
tailscale/tailscale:v1.76.6	        84.04 MiB - older (safe to delete?)

jellyfin/jellyfin:10.10.4	                1.16 GiB	- currently running
jellyfin/jellyfin:10.10.3	                990.36 MiB - older	(safe to delete?)
jellyfin/jellyfin:10.10.2	                990.35 MiB - older	(safe to delete?)

ghcr.io/blakeblackshear/frigate:0.14.1	1.79 GiB - currently running	
ghcr.io/blakeblackshear/frigate:0.14.1-tensorrt	4.54 GiB	- not used
ghcr.io/blakeblackshear/frigate:0.13.2	1.66 GiB	- older (safe to delete?)

louislam/dockge:1.4.2	541.4 MiB	stopped (not in use) 

louislam/uptime-kuma:2.0.0-beta.0	   1.51 GiB - stopped (not in use) 

ghcr.io/motioneye-project/motioneye:edge	643.02 MiB  - stopped (not in use) 	

I want to free up some space and maintain things so that I can keep track of changes, so as to learn a bit more.

I just tried to delete an image that I have in use.

It won’t delete - coming up with an error saying cannot delete

Blimey - could it be that simple? I didn’t dare fiddle for fear of messing something up !

I’ll give it a try on something which is simple to re-install if needs be - perhaps Jellyfin.

Thanks!

I used filebrowser

you could also setup a cronjob with docker image prune -a, which will prune all unused images.

Yes, you can delete any unused images. By default, docker prevents pruning images that are in default, so it should always error if you try to do that.

The old image could be used if you have to rollback to an earlier app version, but Docker will also auto-pull images if they don’t exist locally at that time. So there’s no real need to keep them.

1 Like

This is great information - thanks all. I used docker prune and docker image ls etc. as well as the UI to thin out the unneeded images and containers and in doing so I saved 6 GB of space and tidied up things from various (failed) experiments during the last couple of years.