Apps using primary network interface after upgrade to 24.10

[Bill_Peters]

Hello All,
Before upgrading to 24.10 there was an option in the Apps Config that allowed me to set the network interface to bind the apps to. I had the apps set to my secondary interface. All my proxy configs are pointing everything to that IP address. After the upgrade all my apps are on the primary interface which means that none of my proxy configs work. I can’t find a way to change the interface for docker. Is there a way to do this? I don’t want to have to reconfigure all my apps and proxies, and I would really rather have the apps on a different interface than the TrueNAS GUI.

Thanks,
-Bill

[Bill_Peters]

It looks like docker is using both interfaces so i don’t need to reconfigure anything. I still would rather isolate docker on the secondary interface. But, I can use it like this for now.

-Bill

[J_B]

Hi,

I had the same interrogations about my NIC usages.
Is docker capable of load balancing of some sort or it’s just picking one of the NICs?

I’m really interrested about this topic.

[MartinH80]

not totally sure if this is solving your problem, but…

I had my containers in a specific vlan and was able to do that again after the upgrade to 24.10 using this:

Bind a container in 24.10

Since Truecharts has been removed and metallib follow it. How we can bind a container interface to a specific IP? I try to install a new container and then editing the compose file to bind the IP instead of 0.0.0.0 but even if looking at “netstat” output it seems to works I can reach the container also on other interfaces. Any ideas?

Basically I added the required ip-address for the container to the network interface as an alias and then added the ip-address to the ports section of the yml:

ports:
  - "192.168.24.24:80:80/tcp"

[MartinH80]

hm… although this works for incoming traffic (I can reach the pihole webinterface on port 80), the outgoing traffic (like pihole doing dns requests to its upstream dns server) is going through 192.168.24.100; which is the first alias for the network interface. I can work around this with an additional firewall, but it doesn’t feel right.

[clifford64]

I ran into the same problem because I setup my apps with network segmentation on previous versions. This probably isnt a supported solution, but it’s simple enough for me that its worth the risk.

There is some mention somewhere that they will be adding the feature to control app traffic in 25.04 so it will be similar to 24.04 and earlier.

24.10 Electric Eel Apps Networking

I am doing some tests in preparation for my 24.10 upgrade. I installed a test instance of 24.10 in a VM and have been playing around with it. My current implementation has my apps running on one separate network (10.0.70.0/24) and the normal truenas system running on its own (192.168.50.0/24). 24.04 had settings to specify the gateway for apps, so it used the apps network without issues. I am not seeing a place to specify the network interface for apps. Assuming I am going to have to manually …