Portainer vs Truenas

[claude]

Hello everyone,
When I install a Docker application in Truenas scale it is visible in Portainer.
When I install a Docker application with Portainer it is not visible in the list of Docker applications in Truenas.
Could iXsystems make a modification to correct this?

[bacon]

There exists a feature request for this:

Display non-ix managed stacks and containers on apps screen

Electric Eel includes Docker, and Docker Compose is used to power the apps The apps screen displays IX managed stacks. It would be helpful to also view non-IX managed stacks, and non stack containers. They could be displayed with generic icons, and the Details information could show generic information. docker has a property on all stacks which defines their stack, and containers without this property are not stacks. This would allow a user to understand what containers and stacks are runni…

You can vote on the feature request.

[claude]

Thanks, +1 vote

[claude]

Hello,
Personally I no longer uses Truenas to install applications in Docker.
The only application that I installed via the Truenas catalog is Portainer.
Now I install all my applications in Docker via Portainer from a Docker Compose .yml file.
All my .yml files are stored in a directory which I use as a reference for the configuration of my Docker applications. In case of problem, I can easily rebuild one or more applications from .yml files.

[Stux]

If you like having a directory of yaml files consider using Dockge

TrueNAS Scale: Migrating Sandboxes to Docker in Electric Eel // Compose, Dockge & Jailmaker

[claude]

Thank you Stux for supporting a small and distant user like me from Truenas.
I just installed and tried Dockge. It seems to be a good software, but I prefer Portainer which is clearer to me and seems more complete. Storing .yml files in a protected directory is not a big problem.
Happy end of the year.

[josh]

FWIW, I agree with @claude re: primarily installing apps via Portainer vs the TrueNAS Scale app structure. It feels like I have better control that way. I don’t have experience with Dockge and can’t comment on that, but philosophically we seem aligned.

To the point about storing a directory of yml files, an interesting solution I’ve been working recently with is to link Portainer to a GitHub registry, and storing the yml files on GitHub. I then link Visual Studio Code to GitHub too, edit the files that way and push commits to GitHub. There’s an option to periodically poll GitHub for changes, pull the most recent version into Portainer and recreate the container. The primary concern that I have with this setup is storing secret keys in clear text on GitHub - so far I haven’t done it… However, I looked into it briefly when I started, and as long as I’m careful not to publicly publish my docker-compose git project, they should be well protected.

Interested in the commentary this post creates, if any…