How does inter-container communication work?

[neofusion]

There are (at least) two feature requests related to this:

[Implemented] Inter-app communication in 24.10 Electric Eel

Problem/Justification In TrueNAS SCALE 24.04, it was possible for apps to communicate with each other via cluster.local domain names since they were all on the same network. For example, I use the Nginx Proxy Manager app to reverse proxy to another app on the same TrueNAS machine by using its internal domain name, such as http://immich.ix-immich.svc.cluster.local:30041. In 24.10, this is no longer possible if using the default apps catalog since each app has its own Docker network that is not s…

[MOVED TO ROADMAP] Add support for creating MACVLAN interfaces with "Add Interface"

TrueNAS should support creating and configuring a MACVLAN interface when using “Add Interface”. Ie, MACVLAN should be an option in this menu. [Screenshot 2024-11-27 at 3.38.13 PM] This would prevent complicated CLI scripting in order to create macvlan interfaces and configuring routing tables to allow docker macvlan<->host communication. Macvlan is supported by the Linux kernel and is a well known Linux network type It behaves a bit like a cross between a VLAN and a Bridge. The underlying…