

All of its install steps other than docker compose are still containers, or relate to hosting services, or specific managed platforms.
I’m a simple admin who likes to compile, copy to /usr/bin, prep my system user, populate a directory in /etc with all necessary configs, and write my own .service files.
If you like running single binaries in their own Docker instances, more power to you, but it rubs me the wrong way when people try to force that on me.
NB: I’m not above reading a Dockerfile and executing the steps manually, case in point: that’s how I build lemmy_server for my current instance… but the Immich steps are waay too involved, with too much of the software expecting some less than sane defaults for me. I went through it once, left a bad taste in my mouth, so I stopped using Immich.
Edit: Just to be clear, here’s the installation steps for Photofield. That’s what I like to see. “Download a binary, run, config lives at xxx” - delicious. I also don’t mind doing a ./configure and make if they want me to - just don’t bloat my system with an entire duplicate OS.
That was a coordinated attack that happened for a brief period. As a guy who runs his own home server, trust me when I say it was a nightmare for all involved.
That’s over, now that there are strong protections in place to prevent those sorts of attacks.
Also, if you’re trying to just use something between friends and family you can always turn off federation (E.g. Have matrix act just like the alternatives where you have one network and are only communicating with local accounts).
So glad I don’t have to wake up every morning and purge all remote media from the prior evening 😂