(System specs are in the signature)
I’m fairly inexperienced with docker containers:
- At the moment the only container I’m using on TrueNAS is Plex (the app from the TrueNAS app store with hostpaths configured).
- I am also running another docker container (Duplicacy, a backup software) on an older Synology NAS and I’m planning to migrate this over to TrueNAS.
I’m also looking to add a few other docker containers in the near future and would like to run them on my TrueNAS system as well, since that system is the only server with reasonable CPU and memory specs that I have.
1 At the moment I am wondering how to best organize docker containers on TrueNAS:
- Have a separate dataset for each container (or each stack of related containers) or just one dataset for docker?
- Have a separate user for each container (or each stack of related containers) or not?
2 I’m also wondering, how I should manage containers:
a) Use custom containers in the TrueNAS UI and include my compose.yaml file, as described here: Electric Eel - How I am using Dockerfile, .env files, compose files
or
b) Use software like Dockhand or Dockge to manage the containers
(I see that both of those containers are even available in the TrueNAS app store, so I’m assuming that it is okay to manage docker containers outside of the TrueNAS UI…)
or
c) Forego the TrueNAS docker system altogether and run a separate VM (e.g. with Debian) on TrueNAS and install all containers inside that VM. That would have the usual runtime overhead of VMs, but I’d be more isolated from any change in the TrueNAS ecosystem.
Perhaps I’m overthinking this, but I’d rather avoid pitfalls that I’m not aware of, so I’d appreciate some advice how other folks’ handle this (and why). Thanks so much for your advice.