Apps with separate IP address

Just migrated from CORE to TrueNAS-SCALE-24.10.2.

The app management system seems nice and simple. I’ve got the Plex app up and running easily enough. However, now need to get Transmission up and running on a separate IP as my router can only be configured to route traffic via OVPN by IP (not port).

Have been ploughing through documentation and forum posts, but all the solutions seem to relate to previous versions of SCALE which ran containers on K8s and involve using TrueCharts/ MetalLB.

What’s the prescribed method now to solve this problem? I only know very basic networking and am new to containers. Looking to learn but don’t want to waste time going down the wrong (or unnecessarily overcomplicated) path.

Seems like installing the Portainer app and then using that to implement a custom container config might be the best solution? If that’s the case any pointers on where I should start my learning? What are the drawbacks of using Portainer which I need to be aware of, versus using the IX apps?

Thanks in advance. All help appreciated.

1 Like

For iX apps, per app ips are coming in june, right now there are only a few apps to test the feature. You have to add additional ip aliases to your nic/bridge and then there’s a dropdown on the app install options to choose a nic from the ones you added as alias.

2 Likes

Good news. What would be the best solution until then?

You think I can achieve what I need fairly easily using Portainer?

I don’t use the buildin apps system, i’m running my docker stack from inside a jailmaker jail managed by portainer. I use traefik as reverse proxy to access my apps via domain name, so i dont have a use for per-ip-apps

Similar to @LarsR I use Jailmaker to build my docker stack but with plain vanilla compose instead of portainer and don’t use a reverse proxy. Using Jailmaker is only a band aid until Incus is fully baked in TrueNAS. If you are recently coming from Core and have limited knowledge of containers I’m not sure if heading in the Jailmaker direction now would be a good idea because it is end of life and your time with it would be probably a matter of months at most. If you are flexible on rethinking your vpn at the router level setup consider making your VPN into a container then using rules to route specific container traffic through that VPN. Take a look at Gluetun & Docker Compose.

Perhaps another option would be to setup a Linux VM with the VPN as always on and create your services inside the VM. But that is also EOL with the move to Incus or Instances in Fangtooth. I’m sure there are other options out there. Godspeed!