installing large snaps consumes a load of space in /tmp
Bug #1792933 reported by
Colin Ian King
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I was experimenting with a fairly large binary snap install and noticed /tmp was filling up, one with a multipart file and another snapd-sideload-pkg file:
-rw------- 1 root root 8589942784 Sep 17 15:02 multipart-032184110
-rw------- 1 root root 3910729728 Sep 17 15:03 snapd-sideload-
.. the above is a listing during the install of the snap.
the snap install probably should check that there is enough space in /tmp before filling it completely up. I guess nobody has tried this out with large snaps yet to hit this.
I know my above example is a pathologically large snap, but I am concerned that so much space is used when performing the install.
Changed in snapd: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This was fixed by John recently in https:/ /github. com/snapcore/ snapd/pull/ 6093