Monday, 16 October 2017

Ubuntu - Software Updater and the Insufficient Disk Space

So I'm trying to update Ubuntu 16.0.4.3 LTS using Software Updater, but couldn't get past this: -

    

Now I have LOADS of disk space: -

df -kmh

Filesystem                   Size  Used Avail Use% Mounted on
udev                          16G     0   16G   0% /dev
tmpfs                        3.2G  9.4M  3.2G   1% /run
/dev/mapper/ubuntu--vg-root  2.7T  346G  2.2T  14% /
tmpfs                         16G  224K   16G   1% /dev/shm
tmpfs                        5.0M  4.0K  5.0M   1% /run/lock
tmpfs                         16G     0   16G   0% /sys/fs/cgroup
/dev/loop1                    81M   81M     0 100% /snap/core/2381
/dev/loop0                    89M   89M     0 100% /snap/conjure-up/527
/dev/loop2                    80M   80M     0 100% /snap/conjure-up/745
/dev/loop3                    81M   81M     0 100% /snap/core/2462
/dev/loop4                    89M   89M     0 100% /snap/conjure-up/549
/dev/loop5                    82M   82M     0 100% /snap/core/2898
/dev/sda2                    473M  363M   86M  81% /boot
/dev/sda1                    511M  3.4M  508M   1% /boot/efi
tmpfs                        3.2G   76K  3.2G   1% /run/user/1000

and yet /boot is 81% full.

A quick Google brought me here: -

Not enough free disk space when upgrading

which had me do this: -

sudo apt-get autoremove

and now I have this: -

df -kmh

Filesystem                   Size  Used Avail Use% Mounted on
udev                          16G     0   16G   0% /dev
tmpfs                        3.2G  9.4M  3.2G   1% /run
/dev/mapper/ubuntu--vg-root  2.7T  344G  2.2T  14% /
tmpfs                         16G   52M   16G   1% /dev/shm
tmpfs                        5.0M  4.0K  5.0M   1% /run/lock
tmpfs                         16G     0   16G   0% /sys/fs/cgroup
/dev/loop0                    89M   89M     0 100% /snap/conjure-up/527
/dev/loop2                    80M   80M     0 100% /snap/conjure-up/745
/dev/loop3                    81M   81M     0 100% /snap/core/2462
/dev/loop4                    89M   89M     0 100% /snap/conjure-up/549
/dev/loop5                    82M   82M     0 100% /snap/core/2898
/dev/sda2                    473M  132M  317M  30% /boot
/dev/sda1                    511M  3.4M  508M   1% /boot/efi
tmpfs                        3.2G   80K  3.2G   1% /run/user/1000
/dev/loop6                    84M   84M     0 100% /snap/core/3017

and now I have this: -

which is nice :-)

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...