It is normal that the VLC snap takes care of me:
du -hs /snap/vlc
mount | grep vlc
/var/lib/snapd/snaps/vlc_555.snap on /snap/vlc/555 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/vlc_365.snap on /snap/vlc/365 type squashfs (ro,nodev,relatime,x-gdu.hide)
/var/lib/snapd/snaps/vlc_190.snap on /snap/vlc/190 type squashfs (ro,nodev,relatime,x-gdu.hide)
As I understand it, snap creates copies when updating the application, but is not there an automatic mechanism to keep only 2 versions?
In this case, I’m afraid that space will increase with time.
you are measuring the wrong thing here (the mounted squashfs’es do only present you the uncompressed content of the squashfs, this is not the actual size that is occupied on disk)
to see the actual size of the snap packages themselves something like:
$ du -hcs /var/lib/snapd/snaps/vlc_5*
…gives you the real value
indeed there is additionally also cached data and such which the app creates at runtime. you might want to measure this too:
$ du -hcs /var/snap/vlc
$ du -hcs ~/snap/vlc
there have been discussions to make the 3-snap paradigm configurable, i’m not sure where on the core teams TODO list that stands currently. but as you can see above it would save you far less in reality (196M vs 770M)…
Yes, with that command it actually occupies:
du -hcs /var/lib/snapd/snaps/vlc_5*
But I referred to the documentation:
and that documentation says exactly:
However, these files and folders are mounted from the heavily compressed data that’s stored within the original snap, located in /var/lib/snapd/snaps. These snaps take far less space on your system than their mount points imply
which is pretty much the same i said above do not measure the content of the mount points but the snap files to get a realistic view of the actual disk usage.
Sorry, you’re right, I have not been very careful reading, next time I’ll pay more attention.