Stuck in a loop of freeing up space and filling it up again when rebuilding

[tophee (Christoph)]

@pfaffman

As much as I see you here in surprised you missed it!

Haha, well, I may have missed it or I may have seen it and scrolled past it because I had no reason to be interested in this kind of low level stuff. Database? It’s like the road when driving a car: you don’t really think about it until it gets bad.

It even took me a while to find what you (probably) where referring to now:

Docker base image with PostgreSQL 10 released

launcher has been updated to use the new Docker base image and postgres.template.yml which would use PostgreSQL 10 by default instead of Postgres 9.5. As long as your container’s config is using the default postgres.template.yml, the upgrade of the PostgreSQL data directory would happen automatically the next time you do a ./launcher rebuild. In the event that the PostgreSQL data directory fails to upgrade, please follow the instructions printed by ./launcher rebuild or you may refer to the ins…

But on the way, I found this useful specification of what “not often” means:

@Falco

We upgrade database every two years, and ruby almost every year, for reference.

To summary my lesson from this topic:

The confusion around the original issue was due to a combination of rather rare circumstances which meant that all standard instructions failed for various reasons:

1. two-container setup
2. need for (rare) database upgrade (which requires more disc space than other upgrades)
3. only 20 GB SSD

Points 1 and 3 are still true but probably not nr. 2. Yet, I still had problems doing the web_only upgrade. So the db upgrade probably worsened things but it seems it was a mistake to run the two-container setup on 20GB.