Your focus shouldn’t be on what technologies to use, because you can’t know what will help until you know what you’re trying to do.
Define your use case and the problems you can see now, and the technologies to address them will become more apparent.
I’m trying to indicate that docker has its own kinds of problems that don’t really occur for software that isn’t containerized.
I used the immich issue because it was actually NOT indicated as a breaking change by the devs, and the few of us who had migrated the same compose yml from older veraions and had a problem were met with “oh, that is a very old config, you should be using the modern one”.
Docker is great, but it comes with some specific understanding that isn’t necessarily obvious.
For one, if the compose file syntax or structure and options changes (like it did recently for immich), you have to dig through github issues to find that out and re-create the compose with little guidance.
Not docker’s fault specifically, but it’s becoming an issue with more and more software issued as a docker image. Docker democratizes software, but we pay the price in losing perspective on what is good dev practice.
zfs overlay / docker snapshot issue has been solved since 2021. Proxmox is also well into 8.3, 8.0 has been stable since early 2023.
Sounds reasonable, and I’m sure you’re on your way to solving this.
In my experience thinking hard about my storage needs, I’ve found that as long as I can get decent performance and a bit of redundancy, a solid and tested backup plan can fill in the rest in terms of data safety and integrity.