Old Images Remaining After OpenPanel Update - Any Plans for Cleanup?

naesh

Hey ,

I’ve noticed that after each OpenPanel update, the old container images are still left on the server. Over time, this adds up fast - 1GB or more per update, just sitting there unused:

root@naesh ~ # docker image ls
REPOSITORY                  TAG       IMAGE ID       CREATED        SIZE
openpanel/openpanel-ui      1.2.1     ff8dc680e5c4   44 hours ago   949MB
openpanel/openpanel-ui      1.2.0     efee2a5e466d   4 days ago     958MB
openpanel/openpanel-ui      1.1.9     689621c885ce   8 days ago     958MB
gmt2001/phantombot-stable   latest    c7ffffe5ae61   10 days ago    416MB
openpanel/openpanel-ui      1.1.8     b318d3f34351   12 days ago    959MB
openpanel/openpanel-ui      1.1.7     9fffc7c71cdf   2 weeks ago    959MB
openpanel/openpanel-ui      1.1.6     907487827967   2 weeks ago    959MB
openpanel/openpanel-ui      1.1.5     5e19da5d1b56   3 weeks ago    706MB
openpanel/openpanel-ui      1.1.4     d00eb91435f7   3 weeks ago    706MB
openpanel/openpanel-ui      1.1.3     3a8d7231a9ea   4 weeks ago    705MB
root-openadmin_ftp          latest    682f05cc3893   4 weeks ago    10.2MB
allinurl/goaccess           latest    720849116fe9   4 weeks ago    12.8MB
openpanel/openpanel-ui      1.1.2     f0538b8a56a9   4 weeks ago    705MB
openpanel/openpanel-ui      1.1.1     48e342626535   5 weeks ago    705MB
openpanel/openpanel-ui      1.1.0     1937dd406b84   5 weeks ago    705MB
clamav/clamav               latest    1aa58387b934   5 weeks ago    317MB
gmt2001/phantombot-stable   <none>    2d95814bdcd2   6 weeks ago    416MB
ubuntu/bind9                latest    4e5ea588ccb3   6 weeks ago    166MB
alpine                      latest    aded1e1a5b37   8 weeks ago    7.83MB
openpanel/caddy-coraza      latest    eb181fa86ab9   2 months ago   92.1MB
redis                       latest    43724892d6db   3 months ago   117MB
mysql/mysql-server          latest    1d9c2219ff69   2 years ago    496MB
lazyteam/lazydocker         latest    6518a6686572   2 years ago    55.7MB

I totally get the need to keep one or two previous versions for quick rollbacks - makes perfect sense. But:

Are those old images supposed to stay there indefinitely?
Will OpenAdmin give us the option to manage images (delete old ones, keep only latest, etc.)?
Is there a cleanup mechanism planned to remove untagged or unused images automatically?

Would be great to know if this is on the roadmap. Right now, it feels like storage just keeps growing with every update, and we don’t have much control over it.

Thanks in advance for any info!

stefan

naesh wše just discussed this internally last week.

Images are currently left available for rollback. Back in version 0.3.X, we used to have health checks after updates. If those failed, the system would automatically revert to the previous image with no downtime.

However, those checks are no longer in place, and we’re tagging images now after each version. Starting from 1.2.1, only the latest image will be kept — older ones will be purged.

Reverting will still be possible, but the image will need to be redownloaded.
Currently, there’s no option to set the number of retained images.

1.2.1 deletes all older images
1.2.2+ auto delete previous after update

naesh

Thanks for the update, stefan . That clarifies things.

Good to know that from version 1.2.1 onward, previous images will be removed automatically. This should help reduce disk usage over time. 😃