# Is 30GB now too small to upgrade?

**URL:** <https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435>\
**Category:** Self-hosting\
**Created:** [June 21, 2018, 11:51pm UTC](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435 "2018-06-21T23:51:31Z")\
**Posts on this page:** 4\
**Page:** 1

## AI-generated summary

A user on a Digital Ocean droplet with 30GB of storage is unable to upgrade Discourse due to insufficient space, despite having a small site with minimal media. The disk usage is heavily dominated by Docker and old system files. [codinghorror](/t/-/90435/2) suggests running `/var/discourse/launcher cleanup`, `apt-get autoclean`, and `apt-get autoremove` to free up space. [Amicable](/t/-/90435/3) follows this advice, successfully reclaiming around 10GB of space and reducing usage from 50% to 49%. They then ask if unattended upgrades can be safely configured to automatically manage old kernels and Docker images without interfering with Discourse upgrades.

<div class="post-metadata">

**Author:** ![Amicable](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amicable/32/68902_2.png) [@Amicable](https://meta.discourse.org/u/Amicable)\
**Post date:** [June 21, 2018, 11:51pm UTC](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435/1 "2018-06-21T23:51:31Z")

</div>

I have a Digital Ocean droplet running. I’m currently on v2.1.0.beta1 +149 & was prompted to upgrade docker (successful) before moving onto Discourse. I now can’t upgrade because of lack of space (reports 27GB/30GB & needs min 5GB).

It’s a small site & a handful of users & very few media attachments. Listing out the biggest directories gives me:

- 16M bin
- 1.1G boot
- 2.1G swapfile
- 3.4G usr
- 5.1G lib
- 19G var

then in /var:

| 1.7M | backups |
| --- | --- |
| 24M | log |
| 66M | cache |
| 2.4G | discourse |
| 16G | lib |

then in lib/

42M mlocate  
125M dpkg  
144M apt  
16G docker

Does anything look out of order in these?

Can anyone suggest where I might save enough space to get the upgrade working? Moving up from a 30GB droplet in Digital Ocean doesn’t seem straightforward.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [June 21, 2018, 11:52pm UTC](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435/2 "2018-06-21T23:52:59Z")

</div>

I believe there are existing topics on this, how to clear up space. The TL;DR version is:

`/var/discourse/launcher cleanup`  
`apt-get autoclean`  
`apt-get autoremove`

I was updating a droplet so here’s a before and after those three commands

```
root@talk:/var/discourse# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1005384 0 1005384 0% /dev
tmpfs 204812 21136 183676 11% /run
/dev/vda1 41153856 15600148 23440172 40% /
tmpfs 1024040 584 1023456 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 1024040 0 1024040 0% /sys/fs/cgroup
cgmfs 100 0 100 0% /run/cgmanager/fs
tmpfs 204812 0 204812 0% /run/user/1000
none 41153856 15600148 23440172 40% /var/lib/docker/aufs/mnt/2a8
shm 524288 8 524280 1% /var/lib/docker/containers/f8f

```

here’s the result

```
root@talk:/var/discourse# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1005384 0 1005384 0% /dev
tmpfs 204812 21152 183660 11% /run
/dev/vda1 41153856 11923676 27116644 31% /
tmpfs 1024040 1304 1022736 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 1024040 0 1024040 0% /sys/fs/cgroup
cgmfs 100 0 100 0% /run/cgmanager/fs
tmpfs 204812 0 204812 0% /run/user/1000
none 41153856 11923676 27116644 31% /var/lib/docker/aufs/mnt/2a8
shm 524288 8 524280 1% /var/lib/docker/containers/f8f

```

---

<div class="post-metadata">

**Author:** ![Amicable](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amicable/32/68902_2.png) [@Amicable](https://meta.discourse.org/u/Amicable)\
**Post date:** [June 22, 2018, 8:36am UTC](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435/3 "2018-06-22T08:36:05Z")

</div>

Thank you very much @codinghorror . Docker cleanup gave me back 6 GB or so & the Ubuntu cleanup showed up plenty of old kernels, so another 4GB or so. It’s now maintainable:

```
Filesystem 1K-blocks Used Available Use% Mounted on
udev 487940 0 487940 0% /dev
tmpfs 101608 10880 90728 11% /run
/dev/vda1 30428648 14770996 15641268 49% /
tmpfs 508028 1028 507000 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 508028 0 508028 0% /sys/fs/cgroup
tmpfs 101608 0 101608 0% /run/user/0
none 30428648 14770996 15641268 49% /var/lib/docker/aufs/mnt/800
shm 524288 8 524280 1% /var/lib/docker/containers/618

```

Doing this manually once a year or so seems painless enough, but could I configure unattended upgrades to deal with the kernels & docker? Is this wise on an instance that does nothing but run vanilla Discourse or might it conflict with Discourse upgrade scripts?

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [January 6, 2021, 7:42pm UTC](https://meta.discourse.org/t/is-30gb-now-too-small-to-upgrade/90435/4 "2021-01-06T19:42:24Z")

</div>

Automatically bumped on January 6, 2021, 7:42pm UTC


