DSM 6.2 Deleting images/volumes where "unused" tag is indicated.

[butala]

Hi,

Is it secure or maybe recommended to delete items marked with the unused tag in the image list / volume list in portainer? (I would say it has to do with backups after updates, and thus I could save some wasted disk space, am I right?)

 

[Telos]

I do this occasionally. First, I check to ensure all my containers are running and delete all extra volumes.

Images are easier... I delete images older than my current image.

 

[Akira]

If you're happy to ssh into your system you could use:

docker image prune

To prune any unused images

docker volume prune

To prune any unused volumes
or

docker system prune

To prune any unused images, volumes, networks, stopped containers and build cache

I've got them in my bash_aliases.

 

[fredbert]

I'm a very light user of portainer but what I do use it for is to clear up after the DSM Docker package. The 'Unused' images are left over from when you update a container with a newer image, so I remove them using portainer.

Likewise, I use portainer to remove 'Unused' volumes. But there is a warning (or at least FYI):

The listed volumes are those that are created and used by a container when you haven't mapped a NAS folder to be used as the volume. These volumes will hold any data that is created and maintained by the containers, but when a container is updated in DSM Docker then the associated volume is not carried over to the updated container. Instead, the container will create a new volume with default data... all your accumulated working data is left in the old volume never to be accessed again.​

​

You can SSH to the location and move/copy the old dissociated volume's (directory) contents into the new volume, when the container is stopped. Or you just make DMS folder mapped to the place in the container (e.g. often /data, but not always).​

​

So while I test a container, or if it doesn't create permanent data, then using and removing these volumes is how I use portainer. For all other containers I map DSM folders and these are not in portainer's volumes list.​

 

[butala]

Thanks to all of you!

 

[butala]

Hi, here again with 3 further issues.
I did update the portainer successfully via SSH. Back to portainer I saw 3 unused tags remaining. Two of them I deleted from portainer, except the one tagged as unused on docker:latest with 211 gb. I didn't feel confident to touch it, so is it save to delete this image / and why it wasn't deleted via SSH in the first place? (there is no such container "docker" installed).

The other issue is that I often couldn't update with tag "latest", I always have to try to select the latest by the version number instead to succeed an update. But sometimes even so I can't update, the images installs but is refused get active leaving behing the old versions. What can I do to update it? Appreciate some guidance how to accomplish this via portainer.

I don't understand why some of my containers I have updated shows with double tags like the pict below, and how can I avoid it from occurring, or even can it be corrected.

 

[fredbert]

Those screen shots look like they are from the Images view, they aren't containers. I only see images with two tags the Synology Docviewer. BTW it's not bothered me, unless someone tells me I should be bothered.

The Containers view shows the containers you have, both running and not. The Images and Volumes views should these, respectively, and tag 'Unused' those ones that aren't used by your containers.

Did you once try running Docket inside Docker? I think that is why you have the 'Docker:latest' tagged image.
https://hub.docker.com/_/docker/

 

[butala]

Those screen shots look like they are from the Images view, they aren't containers. I only see images with two tags the Synology Docviewer. BTW it's not bothered me, unless someone tells me I should be bothered.

Thanks for responding me. You're correct, that is the Images view. In fact it doesn't bothers me by having two tags on images anyway.

The Containers view shows the containers you have, both running and not. The Images and Volumes views should these, respectively, and tag 'Unused' those ones that aren't used by your containers.

Here the problem is that after updating image to latest one, the container refuse to accept the updated images and runs further still under the previous image version. Thus, co-existing both image versions but still working with the old version (2nd pict). How can I get this update work as it should?

Did you once try running Docket inside Docker? I think that is why you have the 'Docker:latest' tagged image.
https://hub.docker.com/_/docker/

Have installed the docker in the past (nearly 2 years ago), that time I was totally nub about Docker. As docker docs shows it would be better to delete this image.