@smilebasti The /home/yellowtent/appsdata is the location of apps. This size seems to roughly match the nextcloud size. As for docker, you should not use du tools inside docker's image directories since they are overlays and the du tool is not smart enough to figure out the size correctly. Try docker system df to get a better idea about the actual size docker uses (this is what is reported in the graph as ~5GB). The volumes also link into appsdata so they might be double counted the du tools. To take a wild guess, maybe you were backing up to the file system for some time before you moved to NAS via SMB? If this was the case, then you should remove the old backups manually from /var/backups. You can just safely nuke all the timestamped directories and the snapshot directory inside it.

@fbartels I unfortunately have to postpone. I'll keep https://forum.cloudron.io/post/9623 updated.

For others looking for examples, there's a bunch of custom app templates I made that should help getting started: https://git.cloudron.io/cloudron/tutorial-php-app/ https://git.cloudron.io/cloudron/tutorial-nodejs-app https://git.cloudron.io/cloudron/tutorial-basic https://git.cloudron.io/cloudron/tutorial-redis https://git.cloudron.io/cloudron/tutorial-supervisor-app

Not to mention that if your software is closed source you do not need to publish it for all cloudron users if only you want to use it. With a bit of technical knowledge you can build apps yourself (see the link from @mehdi), push it to a private registry and then use the cloudron cli to install it yo your instance. I am actually hosting a few apps on my Cloudron that I am just building locally (Bitwarden for example before it was available as an official app). If you don't make your app official you are of course on the hook for maintaining it, but you still benefit from the user management of Cloudron, automatic ssl and backups/easy restore. https://simply-how.com/free-docker-container-registry lists a few hosted docker registries that offer free private repositories if you don't want to host your own. Edit: as long as you only need one container you could even use the Docker Hub, as it offers one private image as well.

I can attest that it is definitely NOT a good idea to add more Docker images to a CR box outside of CR. CR assumes it has full use of the box, so, anything additional you add can and possibly will break things

It proved a decent strategy given I get 50MB/s in a direct server-to-server transfer instead of caching it on my computer at a speed of 3MB/s.

@girish Only Bookstack. Yourls installed just fine.

@spdustin Cloudron doesn't support running any services that are not installed via Cloudron itself. So, it won't co-exist with Dokku. BTW, you can build and install custom apps on Cloudron as well - https://cloudron.io/documentation/custom-apps/tutorial/ . It's very similar to developing and deploying apps on Heroku.

I have added information here on how to change the graph driver using a systemd drop-in - https://cloudron.io/documentation/storage/#docker-image-location . Please use it at your own risk, since as mentioned, we haven't tested with other graph drivers.

Thanks @girish! With the above dockerfile cloudron build now succeeds. I have a longer train ride on friday, maybe I can make something happen with bitwarden during it.