Not enough space. Why is that happenning over and over?

Installation
1

When I try to rebuild app on a new instance without files and any activity, I get this info about space limits. I found some links, but didn’t understand how to prevent this situation.
I copied logs, may be they will help.
Questions:

  1. When I rebuild the app, are old images in docker deleted or continue to be there and take their space?
  2. Why I found logs files of a huge size? Do they containg any userful info or I would better deactive logging somewhere? Where can I do it?
  3. How much of disk space is enough for discourse (all files and backups are saved at S3)?
Summary 
`    ./launcher rebuild app`
You have less than 5GB of free space on the disk where /var/lib/docker is locate                                                                            d. You will need more space to continue
Filesystem      Size  Used Avail Use% Mounted on
/dev/vda1        25G   20G  4.8G  81% /

Would you like to attempt to recover space by cleaning docker images and contain                                                                            ers in the system?(y/N)Н
root@natives:/var/discourse# ./launcher rebuild app
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        25G   20G  4.8G  81% /

Would you like to attempt to recover space by cleaning docker images and containers in the system?(y/N)т
root@natives:/var/discourse# sudo find / -xdev -type f -size +100M
/swapfile
/usr/bin/dockerd
/var/lib/docker/overlay2/11f20e584db8fe2a9a04531c4b414ab666235cf459c32e3ab08dcb4991e617da/diff/var/www/discourse/.git/objects/pack/p                        ack-f9771d8b25eca321a22e64342acf3d1a49941948.pack
/var/lib/docker/overlay2/4053159ab17ec99394d754e06638f4243d480e394e0d47326d147c9d252a4c94/diff/var/www/discourse/.git/objects/pack/p                        ack-ffd1b8da21b9e26b4475a3fef6537a89f21989d6.pack
/var/log/journal/9f879a7af4154a4b84d50c11fc294890/system@285e1547c8b243eb817182c10ee45406-0000000000092ee9-0005a4c436c85763.journal
/var/log/journal/9f879a7af4154a4b84d50c11fc294890/system@285e1547c8b243eb817182c10ee45406-0000000000023601-0005a40f35e2b682.journal
/var/log/journal/9f879a7af4154a4b84d50c11fc294890/system@285e1547c8b243eb817182c10ee45406-0000000000039c20-0005a42bdf4f4f6b.journal
/var/log/journal/9f879a7af4154a4b84d50c11fc294890/system@285e1547c8b243eb817182c10ee45406-0000000000065991-0005a462464f08a1.journal
/var/log/journal/9f879a7af4154a4b84d50c11fc294890/system@285e1547c8b243eb817182c10ee45406-000000000000cdd9-0005a3defb4b3ae3.journal
1 Like
2

Docker stores all image you download until you go and remove those.

For convenience, our launcher script will prompt you to run the Docker cleanup if we detect that you have less than 5GB free.

Define huge and what is the exact logging file. We rotate logs by default, but logs scale with the amount of requests.

Depends on the PostgreSQL database size and the Redis cache size.

If PostgreSQL and Redis are also run elsewhere, a small 40GB disk will work just fine.

4 Likes
3

Database is fresh, site is new, I use digital ocean 25GB, increased to 50GB. I don’t use other services to hold PostgreSQL and Redis. In such case what is sufficient?

Now I understand that it’s better to monitor server parameters using digital oceans’ interface.

image
image1268×788 117 KB

1 Like
4

Should be. I haven’t seen much problem with the 40GB that’s on the 2GB droplets. You’ll still need to do a ./launcher cleanup every now and again. It’s darn near impossible on 25GB. It looks like you can keep up to 10GB of backups on https://www.backblaze.com/ for free and it’s reasonably easy to configure.

6 Likes
5

I think Scaleway is offering first 75GB of object Storage for free which should be good to go for a small to medium sized community.

6 Likes