Hi, thanks for the answer! Nothing wrong with Portainer per se, but I have a few specific pain points that pushed me to look for alternatives:
- Git credentials per stack : When my GitHub token expires, I have to reset it in every single stack individually. It gets old fast.
- No TrueNAS GUI integration : Portainer-managed containers don’t show up in the TrueNAS Apps screen, so I’m juggling two interfaces. There are feature requests for this (here and there) but nothing shipped yet.
- Clunky local editing workflow : Right now, testing a config change means: create a dev branch, switch to it in Portainer, test, merge to main, switch back. I’d rather just edit the compose file directly via SSH/VSCode, verify it works, then commit. Much simpler.
- Backup integration : Managing everything through TrueNAS natively should make replication and snapshots more straightforward, though I’ll admit I haven’t fully validated this yet.
So it’s less “Portainer is bad” and more “TrueNAS has its own container management story now, and I’d rather work with one coherent system than bolt two together.”
Mainly, I’d love both to cohexist as Portainer does container management right while TrueNAS is a NAS with some added docker features.
But I’d definitely rather have the stack start-up using a local compose file for faster docker-compose changes and iterations when wanting to try things out before rolling it to production.
Hope it clarifies !