Scale setup for Apps

While I understand how the ports work, I am running a few services and would like to give them a DNS entry.
Pihole.gaut
Qbit.gaut
Galactica.gaut
if they are all just different ports on the same IP, then using the url does not get me to the right place.
today I am using bookmarks to the IP : port and this works fine, but I would like to understand the process to get separate IP for my use case.
thx

Assuming you’re talking about the web interface for those apps, the real way to do that is with a reverse proxy–if you’re using TrueCharts’ apps, that would ordinarily be Traefik; if you’re using iX’ apps, I guess you’d be stuck with something like Nginx Proxy Manager. You then point all the DNS records to that proxy, and that proxy determines which backend service to talk to depending on the name you request. I run dozens of TrueCharts apps this way using Traefik, and it works seamlessly.

If for some reason that isn’t an option, with TrueCharts, you can use MetalLB to expose other IP addresses for your apps; consult their docs for how to do it. I don’t know if or how it’s possible to do this with iX’ apps.

1 Like

OK, so I need to learn Traefik. Probably worth while regardless.
thanks for pointing me in the direction.

Do we expect the Docker containers in Electric Eel to be the same?

Or, don’t use any apps and use the containers from dockerhub directly. This will then translate to Electric Eel. I have 20 apps, all custom apps. It’s very similar to running docker so if you know docker… You can give custom apps their own IP where needed, I do for a few like mariadb and Emby.

Probably not. iX doesn’t have any ingress solution in their catalog at this time, so if they don’t develop it you’ll need to figure it out with some other software. Or do it in a sandbox. Or use whatever TrueCharts is going to come up with.

If you’re using TrueCharts’ apps, it’s very well integrated and their docs are pretty decent.

Just going to add a crosslink to this post in the other thread that speaks to the communicated plan:

We’ll see if they add ingress apps to their catalogue when the implementation matures. It would be reasonable next step.

Once Electric-Eel BETA is out… the Community can add Apps to the community catalog and test the private/internal networks. The goal is let the community innovate with better/easier-to-use tools.

As an alternative to the reverse proxy, you could set up Docker in a sandbox and use macvlan networking to give your containers their own IP address. And with the next version… you will just keep using the sandbox (and if not, what you do in the sandbox should be very close to what Electric Eel will do).

1 Like

Of course, you’ve just thrown away the community’s work on apps so far. It seems likely that’s going to impact “the community’s” willingness to start over.

That’s not quite fair:

  1. All of the TrueNAS community Apps will be ported to the new Docker format

  2. New Apps can be imported using industry-standard Docker Compose

  3. Kubernetes centric Apps can be supported via Sandboxes and/or VMs. Dragonfish is not ending anytime soon so there will be time to transition.

Is it perfect… no. Is it a good pather to easier Apps. We think so.

1 Like

I think it is:

  • You created a k3s-based ecosystem for apps and released it with Angelfish
  • You invited–requested, even–the community to develop apps under that ecosystem
  • The community did, in fact, develop apps, such that the majority of the apps in the iX catalog are “community” apps
  • You’re now throwing that ecosystem away, and all their work with it.

You asked the community to do work in developing apps, and you’re now throwing that work away[1]. There’s no clearer way to say, “we don’t value your work,” and I don’t think that’s going to motivate the community to do more of the same sort of work. Your migrating their work to the new system, if that’s what you’re doing, might mitigate that. “Docker is so much easier” might offset that. I strongly doubt that “you can still run k3s in a sandbox or VM” will at all mitigate or offset it[2].

Maybe I’m speaking out of turn here–after all, I’m not one of the folks whose work is being thrown away. But that’s how it’s looking from the outside.

What does this mean, exactly? You’ve said it several times in this context, but what does it mean? Obviously my Dragonfish installation isn’t going to disappear once EE releases. I assume you aren’t going to pull it from your download servers. But in the past–under FreeNAS, and then under CORE, Release N became EOL nearly immediately upon Release N+1. No further development was taking place on Release N, not even bug fixes, no real support was offered for Release N, and users were told to upgrade to N+1. Is that not the case with SCALE generally? Is Dragonfish an exception? Or do you just mean that “you can continue to use an EOL release if you choose”?


  1. and I’ll note this isn’t the first time iX has pulled a move like this, though I doubt many here remember the iX wiki coming and going and coming again and going again ↩︎

  2. …and to be clear, I’m addressing only the community apps in the iX catalog. I’m not addressing TrueCharts or other third-party app catalogs (if any), though I think many of the same points apply to that context as well. ↩︎

Not true… we expect to migrate 100% of TrueNAS Apps including Community Apps.

Yes, exactly. Users that have custom Applications that may be difficult to migrate will have an extended period to make the transition. Dragonfish is a first class release, it will have a large number of Enterprise users and it will be polished well.

The release of Electric Eel in Q4-24 does not require a transition even during 2025.

There are still a large number of users on TrueNAS 12.0.

1 Like

Just to clarify, I don’t know where this FUD about community apps not being carried over came from. We explicitly stated that all apps in the iX catalog will be moved over, including all the community train ones, which are the bulk of them. We’ve started a list and will be checking them off as they get merged into the new Apps catalog.

Again, this is early, nothing is even ready in the nightly images yet, so check back on it in another month or so. Once existing apps are moved, I expect we’ll move on adding new ones, as well as encouraging community to contribute more if they so choose.

I’m not aware of anyone claiming that community apps won’t be carried over, and I’m certainly not claiming that. But if I’m the one who implemented, say, Tailscale in the current catalog, and you reimplement it in the docker-based catalog, you’re still throwing out my work in favor of the work you did yourself. Right? So in that regard, this:

is good to know as a user, but not relevant to the question.

Yes and no. A lot of the work that went into a Helm chart is pretty directly translatable to the equivalent Compose App. So I wouldn’t say its all being “Thrown out” like that, rather it is being used as a template to help convert to the new format.

That said, if somebody has a particular attachment to their adopted community app, we’re all for them assisting in the migration if they so choose. We’re not going to turn it down, that’s for sure. As we say, pull requests welcome! :slight_smile:

I’d recommend you think of it in classic open source perspective. The original work is used as the basis of v2. The project lives on and the use-case is still supported through both Dragonfish and Electric Eel.

With the transition, its easier to use the App in combination with other Apps.

Okay, what was the question exactly?

This may be the piece I was missing, and would seem to put things in a different light. I’d been thinking you’d pretty much be starting over under the new system.

The question, or rather my claim, was that in starting over on the apps, iX would be scrapping the existing charts along with the ecosystem they worked with. Regardless of whether they’d replace all of them (which they’re saying they will), that sounded like tossing out quite a bit of work done by the community in developing those charts. From Kris’ comment above, though, it sounds as though this is not the case.

I have an SSD boot drive for TrueNAS Scale of which I’m only using 32Gb. Can I setup the apps on that and keep my mirrored 2 drive NAS for storage and data like the Plex database?

No. The boot device is only a boot device.