Not enough disk space for upgrade when Postgres is upgraded

Installation
1

Hello,

Due to a disk place problem, i cannot upgrade my installation since long time.
I’m curruntly using v2.0.0beta1…

I’ve 20gb on my VPS and i’ve 5.6gb free
I’ve alredy delete backups and lot of uploads…

When i try to upgrade, i’ve this:

WARNING: Docker version 17.05.0-ce deprecated, recommend upgrade to 17.06.2 or newer.

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

Unable to find image 'discourse/base:2.0.20171231' locally
2.0.20171231: Pulling from discourse/base
50aff78429b1: Pulling fs layer
f6d82e297bce: Pulling fs layer
275abb2c8a6f: Pulling fs layer
9f15a39356d6: Pulling fs layer
fc0342a94c89: Pulling fs layer
35787b1294ac: Pulling fs layer
9f15a39356d6: Waiting
fc0342a94c89: Waiting
35787b1294ac: Waiting
275abb2c8a6f: Verifying Checksum
275abb2c8a6f: Download complete
f6d82e297bce: Verifying Checksum
f6d82e297bce: Download complete
9f15a39356d6: Verifying Checksum
9f15a39356d6: Download complete
fc0342a94c89: Verifying Checksum
fc0342a94c89: Download complete
50aff78429b1: Verifying Checksum
50aff78429b1: Download complete
50aff78429b1: Pull complete
f6d82e297bce: Pull complete
275abb2c8a6f: Pull complete
9f15a39356d6: Pull complete
fc0342a94c89: Pull complete
35787b1294ac: Verifying Checksum
35787b1294ac: Download complete
35787b1294ac: Pull complete
Digest: sha256:5452defe724d2940ae2fd11ec690fbcd1d49cf7607ca9044502f2817c0f76647
Status: Downloaded newer image for discourse/base:2.0.20171231
You have less than 5GB of free space on the disk where /var/lib/docker is located. You will need more space to continue
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        20G   16G  3.8G  81% /

Would you like to attempt to recover space by cleaning docker images and containers in the system?(y/N)y
WARNING! This will remove:
        - all stopped containers
        - all volumes not used by at least one container
        - all networks not used by at least one container
        - all dangling images
Are you sure you want to continue? [y/N] y
Total reclaimed space: 0B
If the cleanup was successful, you may try again now

What can i do?

Ncdu tell me that:

--- /var --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
.  12.6 GiB [##########] /lib
    4.4 GiB [###       ] /discourse
   65.0 MiB [          ] /cache

--- /var/lib ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   12.4 GiB [##########] /docker
  142.2 MiB [          ] /apt
   43.0 MiB [          ] /dpkg


--- /var/lib/docker ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   12.1 GiB [##########] /aufs
  315.7 MiB [          ] /containers
   15.4 MiB [          ] /image
   60.0 KiB [          ] /network
   28.0 KiB [          ] /volumes
   20.0 KiB [          ] /plugins
e   4.0 KiB [          ] /trust
e   4.0 KiB [          ] /tmp-old
e   4.0 KiB [          ] /tmp
e   4.0 KiB [          ] /swarm

Is it normal?
Thanks

2

I don’t know how advisable it would be for a live site, but I have had this issue with one of my localhost intstalls I use for testing/development.

What works for me is skipping the prerequisites check i.e.
./launcher rebuild app --skip-prereqs

1 Like
3

I Think there is a pending postgres update there. That will definitely need more disk space. Skipping prerequisites may result in a failed upgrade! isn’t it?

1 Like
4

Good point. I haven’t updated that install since before the Postgres version upgrade so I may end up losing that one. Being a non-live forum the loss would be a disappointment, but losing a live forum would be much more of a problem.

1 Like
5

Also, the docker version is outdated, That needs an upgrade first.

6

Thanks guys

Can i upgrade docker alone easily?

7

Yes, upgrade Docker first, there is no risk there and it should be done anyways.

The Postgres 10 upgrade does require enough disk space for a copy of the current database, so that’s the source of the issue.

8

Hello,

few days later, i’ve upgraded docker to the latest version, but the problem was the same.
I’ve solved the issue by changing my vps provider, ovh to digitalOcean. More space and lowest price :slight_smile:

Thanks

3 Likes
9

This topic was automatically closed after 2223 days. New replies are no longer allowed.