I am trying to get bridged connection for apps but it does not seem to be applying properly.
Per app IP seems to be the correct function but despite being active for about a year there still doesn’t seem to be a documentation page.
I can get a second IP assigned sort of. There are two bugs a haven’t been able to solve yet:
The app will not pull a DCHP IP from my router like a VM will, so IPs have to be manually assigned.
The management interface is somehow still listening on the app assigned IP, so I cannot assign port 80 to it.
How do I get a virtual NIC linked to the bridge like on a VM?
Also can anyone explain what exactly the “Host Network“ checkbox does?
It sounds like it should be the option for a bridged / direct to network connection but it clearly isn’t.
This can’t be accomplished through the apps UI. You’ll need to use the Docker network CLI to create per-app bridges, and the TrueNAS network UI to create per-app bridge interfaces, each on a separate subnet. You may also need to configure a VLAN interface on the TrueNAS and infrastructure sides underneath the per-app bridge interfaces, and create static routes per-VLAN.
Is this really worth the vast increase in complexity? The bridges can’t exist on the same subnet without causing serious spanning tree network loops.
Thanks for the info.
At this point, probably not. I was trying to move some things out of VMs and into containers for more efficient resource allocation. It’s not the 1st time I’ve tried but this is the farthest I’ve gotten.
I’m not sure why TrueNAS is currently being built with such a hostile attitude towards customization but features seem to dropping left and right.
You misunderstand the design intent of TrueNAS. Apps are a nice-to-have feature, as are VMs. They’re conveniences for low-effort use cases. TrueNAS is first and foremost a storage appliance. Any “customization” that jeopardizes the stability and safety of this primary function is jettisoned without a second thought or not included in the first place.
