Static IP for Apps from catalogue?

I’ve figured out how to set static IP addresses for custom apps on TrueNAS SCALE, but I need to be able to set static IPs for apps from the Discovery catalogue.
Is there any way of doing so? I found it easy to do back on TrueNAS Core, but I haven’t figured out how to do the same thing on SCALE yet.
I am running a motherboard with two built-in 1GbE ports, and I can install another network card if needed.

Are you referring to Truecharts? Or the IX community apps?

My server has a static IP address which I take advantage of but I haven’t seen the need to have a static IP on the application server because they’ve never changed on me. Is this a problem that you’ve run into recently?

All I’ve ever needed is the static IP address for the server and the port number that the application happens to be using.

I use static IPs to separate my public services from my local services.

OK, so it looks like you want a specific application to use a specific network interface card on the host correct?

I’ve been trying to learn not so successfully thus far how to take advantage of the nginx proxy manager. That might be an app that would be useful to you. I can’t say for certain because I don’t fully understand it yet.

I’m not the OP (original poster) though.

Sorry I replied to you by accident rather than the original poster. They should see the post anyway hopefully.

I use nginx without any issues. It reverses with no issues to the Scale serve + port. My websites, etc. go through to the wordpress installations, no problem. But DNS servers require a static IP address. And few, if any, of the TrueNAS catalog apps allow a static IP assignment in the setup.

Hi,
Before this goes into the tomb, anyone have a solution for this !?
I’m starting to have more and more applications within the truenas scale and would like to isolate their communications.
Using the official apps, I also didn’t find any configuration to either use the host network (dhcp) or a subnetwork dedicated (for example, behind traefik)
Thanks in advance!

Fundamentally, there are two ways to do static ips with docker containers,

One is to bind a port to an ip,

Vote for this :wink:

The other is to create a macvlan network and then attach the container to that network, where you can then specify the IP on the physical LAN.

Which I suspect would come after the bind ip option.