ZeldaFreak

To be more specific: Postgresql requires manual steps with major versions. Tutorials I found require you to dump the database in the old version first, then update and then import. You could use a tagged version of postgresql and just auto update there but the main container might require a newer version. I saw containers who try this but none looked production ready.

Yeah I expected that this would happen. They already did this with RAM. They just rebrand RAM, sell it for a way higher price and add a check. When they brought their own branded HDDs, I knew they will pull of the same scam.

Building an own server isn’t that more expensive and you don’t have to deal with the whole lockout with Synology. For example I had quite the issue to access hardware. I wasn’t able to get Home Assistant running on my NAS. The issue was my Zigbee USB Stick. I got it running to the point where I was able to send commands (e.g. turn on or off lights) but the status didn’t came back. I threw it on my Pi3 (now Pi5) and zero issues.

The next NAS is self build. Probably Proxmox as base, with truenas or so as main server and the rest depends on what I might need.

Auto updates can cause problems. Some recommend it, some tell you to not do it. My standpoint is, when a container can’t work with auto updates, they suck. Sure there are containers who require some additional attention after an update, like gitea with some config changes but I use it in an environment where it can be offline of some time.

If a container uses Postgresql, you can’t auto update. So far I didn’t found a well maintained container, that can do this. You also should keep an eye on your containers. As I mentioned, Gitea had some config changes, breaking the default theme (nothing major). They even screwed up their tags and I had 3 times an RC in a tag where no RC should get published. With Jellyfin I was on a tag that didn’t got any updates anymore and I needed to use a different one.

Auto update. Works like a charm, except PostgreSQL. For me it’s good enough and even though works with containers, where they don’t recommend it. I do have backups and for my private time, I don’t get paid, so it should be as maintenance as possible from my side.

I do check from time to time if something is broken and I noticed a container where they removed a version tag, I was using. The “biggest” thing that was broken, was my gitea server where they changed the config for the default Theme.

Also that’s why I hate PostgreSQL. It requires manual labor for updating. Had a recipe Docker and they cut support for previous major version quickly. Not good. That stuff could break, ist an option with every update. This is why backups exist. As a single user, it’s not a problem. For a big system, I wouldn’t do auto updates, so I can check if everything works.