I just wanted to link this post where I documented the Nextcloud AIO update process, which includes a cleanup step to remove old Docker images after the update is completed.
Looking at your output, it seems you skipped or missed that part — you still have duplicate images from the previous registry (nextcloud/) alongside the current ones from ghcr.io/nextcloud-releases/.
For example:
nextcloud/aio-collabora latest 21a697112d03 2 months ago 1.43GB
ghcr.io/nextcloud-releases/aio-collabora latest b0cdb0003737 2 weeks ago 1.43GB
This is a clear case where the older image is likely unused and can be removed to free up space.
Migration to the new ghcr.io registry
You might have noticed that some of your images come from the nextcloud/ repository, while others are from ghcr.io/nextcloud-releases/. This migration to the new ghcr.io registry was necessary due to Docker Hub limitations — as of April 1st, 2025, anonymous pull limits were reduced to 10 pulls per hour.
To avoid update failures and image pull issues, Nextcloud AIO moved its images to ghcr.io, which doesn’t have these restrictions.
Source – help.nextcloud.com
That’s why it’s important to remove the old nextcloud/ images and use only the ones from ghcr.io/nextcloud-releases/.