Portainer = more complex for handling docker but has more features
if you use a Truenas App you cannot not mange the app in Portainer or Dockage, or at very best is limited.
Background
I can program a little but I have never used docker and really want a GUI to handle everything until I know better.
The information from TrueNAS on the best way to setup your App ECO-System is completely missing (unless I missed it). Is there any?
I want to use TruneNAS apps as they are easy to setup and use, but I might like to use Portainer or Dockge to manage them they have a much better developed GUI than TN.
I do not particularly want to get locked into Portainer or Dockge and then find out that to use TN features I should not of used them.
Questions
How do people setup their TN Apps environment (data, configs, hostpath)?
if you use Portainer or Dockge does that not make the TN App catalogue pointless?
What is the best way of bringing in external dockers? Do you use Portainer or the inbuilt TN method. Are there package managers for Docker?
What do people use for an ideal hostpath layout for the configs and data for the various dockers.
Per App IP, is this simple to do or is it worth waiting for TN updates to make this simpler.
A guide, or YouTube Video covering all of this would be great, but one that explains things as they go along and not just for their ego trip . I like standards and tried and tested setups, there is no point in re-inventing the wheel.
I recommend against it. iX has abandoned three previous apps ecosystems after finding they were ātoo much workā to maintain (i.e., they were unable or unwilling to devote the necessary resources to maintain them); nothing Iāve seen gives me any confidence that their resources or priorities have changed such that this apps system will be different. This is obviously subjective, but I fully expect iX to abandon maintenance of the apps catalog in due course.
Not necessarily. First, I expect most of us who use Dockge or Portainer do so using the iX apps (though itās certainly possible to run them without the app). Second, nothing prevents you from running some iX apps, and other Compose stacks using Dockge or Portainer.
As far as i know you should also be able to add networks and env variables to it
(but then again i only use 2 official apps, peanut and scrutiny) the rest is deployed in an debian lxc and managed by portainerā¦
As far as I know, yes, but I donāt use Portainer (I use Dockge). And other than Dockge, Tailscale, and Scrutiny (whose usefulness I question, but since iX is ripping out most of the SMART functionality it doesnāt seem like I have a choice), Iām using Dockge to handle the rest of my stacks, so Iām not too interested in its ability to manage the TrueNAS apps.
How do people setup their TN Apps environment (data, configs, hostpath)?
Pretty much as per Stuxās video linked above. I never used any docker apps until about a year ago, then rapidly learnt once Kubernetes was abandoned by Ix. It didnāt take long to learn, and I since transferred everything across to docker apps (web server, UniFi controller, Syncthing) except Home Assistant. And Iāve since set up arr, Immich, Stirling-PDF, openwebUI, CUPS, Crafty Controller, nextcloud and jellyfin, all updated using watchtower. Itās very easy to maintain!
I have /mnt/tank/docker as my main dataset, with ādockgeā and āstacksā datasets under that. In stacks, each docker container has its own folder of course, which I can easily access using Filezilla / WinSCP etc.
if you use Portainer or Dockge does that not make the TN App catalogue pointless?
For me, mostly. Although I use the āofficial TN appsā for Dockge, scrutiny and miniDLNA (I couldnāt get that to run/network properly under Dockge for some reason)
What do people use for an ideal hostpath layout for the configs and data for the various dockers.
most of my apps compose files use the following (as an example):
- /mnt/tank/docker/jellyfin/config:/config
. I like standards and tried and tested setups, there is no point in re-inventing the wheel.