If I read this correctly, Immich is setup entirely through Ansible, no docker compose. That's fine, however if Immich changes something drastically in their setup topology, it'll be more work for you to implement those changes. For services that use docker compose, you could use Ansible to deploy a compose file in a dir, say /opt/immich-docker along with its requisite .env and other files. Then setup running it via systemd. Then when you need to update it, it's almost copy-paste from the upstream compose file into your Ansible repo.

Nice work!

I'm unsure but I see secret.yml in there. Is that sensitive? You might want to update that ASAP if it is.

Nice, well done. I wish I could find the same for Debian.

I'm curious how using ansible to deploy docker containers is easier than just using docker compose?

Ansible makes sense to setup the OS the way it needs to be (file systems, folder structure etc), but why make every container through ansible instead of just making a docker compose and maybe having ansible deploy that?

Even easier is probably to just run something like portainer and run the compose file through there

In a similar situation. I was using Open Media Vault but it has some networking bug that I just can't nail down or work around. I have to manually fix the networking every time it breaks. Otherwise I barely used OMV features and did most things through Docker. I'll be switching to Diet Pi and probably Ansible unless I feel like learning Puppet.

I’m curious what issues you had with TrueNAS? I’ve been using it for about a year now and the only issue I have had has been with one of my pools deleting itself after a reboot, but that was user error because I put the wrong SED password in the settings.