Question about Snaps

[Oliver Grawert]

hi,
On Do, 2016-10-06 at 17:09 -0500, Chris wrote:
> Reading this thread - What's happening with 16.04 & 16.10? 100% of
> RAM
> being used by nothing - I got curious and ran df -h on my 16.04.1LTS
> box. Everything looks just fine but I've a question about the a snaps
> allocation when it's upgraded to a newer version. As seen below:
> 
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/loop2       82M   82M     0 100% /snap/wallpaperdownloader/3
> /dev/loop3       12M   12M     0 100% /snap/vtop/3
> /dev/loop1       97M   97M     0 100% /snap/wallpaperdownloader/4
> /dev/loop0       75M   75M     0 100% /snap/ubuntu-core/423
> 
> there is the snap core itself in /dev/loop0. The question comes about
> with 'wallpaperdownloader' /dev/loop2 (version 2.1 of the snap) and
> /dev/loop1 (version 2.2 of the snap). Ignore the vtop snap as it's
> not
> being currently used (disabled). Should I be able to remove the
> ~/snap/wallpaperdownloader/3 and release that 82M of space or how
> should that be done?
> 
by default snapd always keeps the last version around so you can use
"snap rollback"... if you want to explicitly remove a revision you can
do:

snap remove --revision=3 wallpaperdownloader 

the mailing list for snap users and developer is:

https://lists.ubuntu.com/mailman/listinfo/snapcraft

and for porters of snap images to specific hardware (RPi and other
boards, routers, robots, appliances, switches, servers etc):

https://lists.snapcraft.io/mailman/listinfo/devices

ciao
	oli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20161008/84d4cc17/attachment.sig>