You’re right that there are many large images on your system, and based on your list, a good example of a duplicate would be:
nextcloud/aio-collabora latest 21a697112d03 2 months ago 1.43GB
Since the same component now exists under ghcr.io/nextcloud-releases/aio-collabora, this older image is almost certainly unused and safe to delete.
Regarding Portainer:
It’s a common misconception, but Portainer does not require images or containers to be created from within Portainer itself. Once installed, it connects directly to the Docker socket (/var/run/docker.sock) and provides full control over all:
- Images
- Containers
- Volumes
- Networks
— regardless of how they were created (CLI,docker-compose, or other tools like AIO).
Personal note:
In my case, I never use Portainer Stacks. I always deploy my containers via docker-compose.yml from the CLI.
Why? Because I’ve had multiple cases where configurations inside Portainer Stacks simply vanished after a Portainer update.
Since then, I use Portainer only as a management dashboard — and it works great for that.
Suggested cleanup process:
-
Delete the
nextcloud/aio-collaboraimage manually using:docker rmi 21a697112d03That will free up ~1.43 GB.
-
Install Portainer, which pulls an image around 420 MB — so you’ll have enough space after removing Collabora:
docker run -d \ -p 9000:9000 \ -p 9443:9443 \ --name portainer \ --restart always \ -v /var/run/docker.sock:/var/run/docker.sock \ -v portainer_data:/data \ portainer/portainer-ce -
Open Portainer in your browser (usually at
http://<your-ip>:9000) and:- Go to Images
- Use the “Unused” filter
- Safely delete all remaining duplicates or old images
That way, you’ll recover disk space while having full control and no risk of deleting something essential.
Note: This post was written with the help of an AI assistant as a writing aid only. The opinions, solutions, and technical recommendations are fully based on my personal experience.
More about how and why I use AI to write forum posts:
Is there limitations to installing Nextcloud via CT template on Proxmox - #4 by vawaver