Techno Tim, docker container truenas workflow

Apps and Virtualization
21

Having now watched the video, I don’t see that Tim’s method allows you to create/use custom Docker networks (e.g., to put your various apps behind a reverse proxy). Though I guess you could still do that at the CLI.

And really, it looks like a way to use a few pieces of software to cobble together something almost, but not quite, as good as Dockge.[1] Yes, the individual apps will show up in the TrueNAS UI, along with minimal and inaccurate resource usage statistics. OK, I guess, if that’s your thing.

Though his plea at the end to the TrueNAS team to “please don’t break this” definitely resonated. Let’s see how long it takes them.

  1. Although using code-server means that you have a full browser window to edit files, and thus the line wrap/numbering annoyance with Dockge won’t be present. ↩︎

1 Like
22

Docker networks are specified if desired in the compose.yml file. I use them in all of mine.

And basically all of mine are behind a reverse proxy, caddy, and using caddy labels even.

I prefer it was a placeholder until Truenas improves the custom yaml function. At that point, the include is not needed but the compose remains the same. Just like people who want to use experimental instances until Truenas improves that function.

People have converted Truecharts → nspawn → scale docker → dockge → instances, if that’s your thing keep changing everything. And, I’ve seen many post that as soon as Truenas improves the custom yaml function, they’ll abandon dockge, lol.

Here’s my simple handbrake compose:

services:
  handbrake:
    restart: unless-stopped
    image: jlesage/handbrake:latest
    env_file: .env
    expose: 
      - "5800"
    volumes:
      - /mnt/tank/NoBackup/Handbrake/Data/Input:/storage
      - /mnt/tank/Data/Handbrake/Config:/config
      - /mnt/tank/NoBackup/Handbrake/Data/Output:/output
    labels:
      diun.enable: true
      caddy: handbrake.mydomain.tld
      caddy.reverse_proxy: "{{upstreams 5800}}"
      caddy.import: encode
    healthcheck:
      test: ["CMD-SHELL", "wget --no-verbose -T3 --spider http://localhost:5800 || exit 1"]
      interval: 1m
      timeout: 10s
      retries: 5
      start_period: 30s
      start_interval: 5s
    pull_policy: missing
    cpus: 8
    networks:
      - Handbrake
      
networks:
  Handbrake:
    name: fatula
    external: true
1 Like
23

Shaking your handbrake for the NoBackup dataset.

1 Like
24

Yeah, it’s just a temporary location until I move it elsewhere. Actually, generally, it gets downloaded and I work on that output for various purposes before moving to the final Emby location. A lot of my data is NoBackup! But it’s all unimportant stuff like this. I think I have more than a TB of NoBackup.

25

I wouldn’t abandon Dockge for TrueNAS’ native feature, at least until the latter places the Compose files on disk somewhere where I can easily back them up. And, of course, create a UI that doesn’t suck.

Or iX can stop pretending they care about apps at all and just start using a decent third-party GUI frontend for Compose.

1 Like
26

Yeah, if they did settle on a third party GUI frontend, I’d be fine with that. I realize you wouldn’t abandon, but I can’t believe the stuff people keep converting, so much time. I don’t mean the people who know what they are doing, I mean newbies.

Using the technique noted, they are backed up of course. Just a placeholder until better days come.