Custom Apps, YAML, and Resources

Apps and Virtualization
1

I can’t seem to find a clear answer, but is the docker compose way of defining resources valid for TrueNAS Scale (24.10+)?

Does TrueNAS Scale have defaults to this?

deploy:
  resources:
    limits:
      cpus: '8.00'
2

Yes, this is valid. See the examples here: Installing Custom Apps | TrueNAS Apps Market.

1 Like
3

I use Portainer to do this, but yes it works fine. I have the portainer agent installed in TrueNAS (in my case installed from the command line) and I also have Portainer running on a couple of other machines as well. Using my main portainer instance, I can access any of the machines I have running docker images.

I use yaml files, but I copy them into Portainer using the “stacks” feature. Works the same as compose, just has a GUI in front of it. Inside of TrueNAS I use generic volues for my docker volumes, and I just bind mount my volumes. Works great, its super fast, and nothing breaks if there is an update to TrueNAS. The other benefit is if you want to use a custom image, like say something linuxserver.io, that is also quite easy to do this way.

4

When you say there’s a benefit [to using Portainer?] if you use a custom image, what benefit are you thinking of?

The built-in YAML feature does not care what repository you point it at, at least as far as I can tell.

5

I read that, not sure why I missed the section I was looking at there.

6

This is true, but the problem is that the built-in yaml feature just plain sucks.

With Portainer or Dockge (my preference, it’s a lot simpler and easier than Portainer), you can easily keep track of all your installed apps, see the yaml files you used to install them, and also add .env files which are commonly used with images from places like linuxserver.io. The built-in yaml features does NOT allow you to use and maintain an .env file, so you have to modify the yaml file to include anything in there. Also, the built-in feature doesn’t save your yaml file or allow you to edit it: it saves a different version of the file, stripping out comments and re-arranging everything. It’s just terrible, and I don’t recommend anyone to use it.

7

No, but you can include files from wherever you like on your system, which gives you a similar effect. I still prefer Dockge though.

8

The built-in method lets you edit and save. It does however not offer versioning, you can only have one current version.

That and the bit about reording and removing comments are valid points.

I work around that by editing my YAMLs in my main OS and copy/pasting them into the YAML-window in TrueNAS. It works well enough for me and gives me full control over the files in question while letting me edit the files using the editor of my choice.

I run several containers published by LinuxServer and am very happy with the result.

Using Dockge or Portainer is fine for anyone who prefers it, I was just curious if I had missed something. I value not having the added layer of complexity an app manager introduces higher.