seeded snaps never cleaned up.

Bug #1796165 reported by Scott Moser
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Confirmed
Undecided
Unassigned

Bug Description

Changes in the ubuntu images (bug 1796137) make it seem that seeded snaps are never cleaned up. Or at very least they are lazily cleaned up.

Do the seeded snaps just forever take up that space?

root@c1:~# ls -lh /var/lib/snapd/seed/snaps/
total 154M
-rw------- 2 root root 88M Oct 3 03:55 core_5548.snap
-rw------- 2 root root 67M Oct 3 03:55 lxd_8959.snap

root@c1:~# cat /etc/cloud/build.info
build_name: server
serial: 20181002
root@c1:~# uptime
 18:57:04 up 4 min, 0 users, load average: 0.89, 0.85, 0.61
root@c1:~# cat /proc/uptime
263.00 245.00
root@c1:~# snap list
Name Version Rev Tracking Publisher Notes
core 16-2.35.2 5548 stable canonical✓ core
lxd 3.5 8959 stable/… canonical✓ -

root@c1:~# snap version
snap 2.35.2+18.10
snapd 2.35.2+18.10
series 16
ubuntu 18.10
kernel 4.18.0-7-generic

Revision history for this message
Gustavo Niemeyer (niemeyer) wrote :

Yes, somewhat by design. The seed directory was cooked to be read-only so that factory-resets can bring the device back into a pristine state.

That said, we may find cases where this is irrelevant and destroying the seed is acceptable. That logic does not exist today, and we'd have to be pretty careful about it given that the seeding is not an atomic operation.

Changed in snappy:
status: New → Confirmed
Michael Vogt (mvo)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.