Cloudron won't update - No backup site for update

[potemkin_ai]

ahm... there are no backup sites...

[nebulon]

that would explain it, then you have to first add a backup site. Any auto-update will only work if a backup can be made.

[potemkin_ai]

but I don't need a backup for that site... any way to specify some kind of /dev/null for such a case?

[robi]

@potemkin_ai you try local?

[potemkin_ai]

apart from the fact that it's not needed - there is not enough space for that

[nebulon]

So Cloudron will always require a backup for auto-updates, there is no way to skip that unless you update manually.

[potemkin_ai]

Ok... it's a pity thought...

[goseph10]

@potemkin_ai Idea: Use Amazon S3 Glacier Deep Archive. Its only 1$ per 1TB. Adds some more cheap Backup.

Or local should work, just exclude your Apps and only backup Cloudron. Its small.

[potemkin_ai]

@joseph , thank you! It's not that I don't have space (I have a few TBs idle) - it's that I don't need it.

Local won't work - because the server has not enough space for the local. And Amazon is only cheap, unless you really start to use it

[robi]

@potemkin_ai then install rustfs, minio, or seaweedfs on another Cloudron with space and do a backup. Easy peasy.

Even as a one time thing the demo server can help.

[potemkin_ai]

@robi like I’ve told - I do have where (few TBs served via S3).

It’s just that I do not need a backup for that.
Given that I can do update skipping the backup, an artificial limit on automatic backup is something I’m not clear about.

[robi]

@potemkin_ai then it's not clear what you're asking as your statements seem confusing and contradicting.

You are not stuck, you have many options. Now what?

[potemkin_ai]

I was under impression I'm quite clear... I don't think the decision made by authors correct.

I'm forced to do the backup, even though there is no technical requirement for that. I'm forced to do the backup the way authors want, even though I have my remedies.

As a result, I've just found out one Cloudron instance seriously out of date with a Docker security vulnerability in it. Just because authors decided that I have to have a backup to have automatic backup - to have my systems up to date.

Not sure I follow that...