Cloudron Forum

Maybe you have dangling images around, which are not deleted, can you see if docker image prune -a removes some?

Tyvm, saved my day!

@girish I recall you making that run automatically..

Should it run more frequently?

@Neluser Good idea. But it's quite complicated to automate things like this, that's what it's not done. But something to keep in mind. In the meantime, following https://docs.cloudron.io/storage/#docker-images is the way to go.

The validation code seems to be at https://github.com/hay-kot/mealie/blob/8d79773bf65eb6bfd9021963324d53a25aab3cde/mealie/routes/admin/admin_about.py#L62 however I don't quite understand what it tries to check here. I don't think this is relevant on Cloudron though.

Also, in Cloudron 7.3.x, all the addons/services are still using the old base image (3.2.0) but the apps have all been updated now to use the new base image (4.0.0) . In 7.4, all the addon docker images are updated to 4.0.0. You will see some space savings after the update.

@hovinen Ah yes! docker returns 404 it seems when it doesn't have enough disk space to store images. I remember this (again) now. Unfortunately, the API has no way of detecting this.

@robi
On that, I don't have the data or experience to talk.
But 100% sure you can't use wasabi latency, I think smb or better NFS should be a better option, but I'm not an expert.
and Using so much ram for it, im not big fun about it, but I would have to try it before to have a real feedback

See https://forum.cloudron.io/topic/8101/fix-for-kernel-bug-in-ubuntu-20-04-causing-various-issues for a solution.

@Kubernetes said in 15MB Rust Written Private Hostable IM Social Chat App:

Tagging @LoudLemur

Thanks. V busy at moment. Will hopefully have a chance later next week.

@girish many thanks !

@wind-gmbh said in Silverblue - for container-based software:

But unfortunately No in regarding the ton of work that could be necessary to support Cloudron.

There is another important aspect as to why Ubuntu is the underlying platform for Cloudron. A lot (if not all) hosting providers are offering servers with this os preinstalled, which makes it easy to get started with Cloudon. If MicroOS would be the (only) supported choice then Cloudron users would be limited to hosting options which either provide it by default, or allow admins to install their own os (which could be a challenge for some).

If I remember correctly both Nebulon and Girish are former Suse employees, so I'd wager they would be biased towards MicroOS otherwise 😄

@girish great thanks, It works 😉

@ei8fdb right the graphs don't update immediately, but every 6 hours or so. Otherwise, the disk spins a lot 🙂

I will mark this thread as solved, but this problem will go away soonish. I think only ~20 apps are left to use the new base image. The 7.1 release also updates all the internal containers to use the latest image. Should all be done end of this month.

It's back online now!

Agree about having a second source. Ideally, we can have some self-hosted docker registry which is used as a fallback for such situations.

Flatpack and Appimage formats do not provide the kind of process and filesystem isolation that Docker does. I would not be comfortable running run a service like Cloudron if it allowed running things other than well-defined/managed containers.

Yes, there are ways to break isolation and escalate out of a Docker container, but flatpack apps can, essentially, write anywhere on my system. Updating the ecosystem is also much more difficult; by comparison, it is possible to auto-build Docker containers from source and track recent updates/manage timely security vulns in a way that flatpack/appimage packages do not/rarely do.

@girish said in Docker Container - Unable To Install Cloudron:

@brutalbirdie said in Docker Container - Unable To Install Cloudron:

Maybe adding Docker in there as well to prevent confusion.

Done!

The fast guy! 😄

@fortytwo said in How to delete unused docker images ?:

Scaleway S3 Object Storage with 75GB free

Is this for your backup? Cloudron does not backup images (and code), just your data. From your screenshot, it's only going to take 1.13G (nextcloud) + 6.5M (bitwarden) + 520K (box) + 212K (email). So, it's way less than 2GB per backup. If you store like 30 full backups, it's still under your object storage.

We use what is called immutable infrastructure for this if you want to learn more.

Nice!

Properly open source and maintained forks of Elasticsearch and Kibana

https://github.com/opensearch-project/OpenSearch

https://github.com/opensearch-project/OpenSearch-Dashboards