FEATURE REQUEST: Allow apps to have their own IP in Electric Eel

Problem/Justification
Add ability to use separate IPs on apps in Electric Eel. With GUI manageability.

Impact
It will be similar to a CORE jail.

User Story
I don’t think this needs much of a story. It’s very practical to have apps using their own network stack.

2 Likes

i.e. allow the creation of a macvlan or ipvlan network from the TrueNAS GUI.

This is planned for Fangtooth but may not make Electric Eel.

The workaround is to use Dockge.

1 Like

Here’s an alternative to this request, which I think is more practical for inclusion in EE, even post release.

The difference is this is not providing a dedicated IP to a container/app, but rather allowing an app to to bind a port to a specific IP, which is created as an IP alias on a network interface.

I have already tested and this does work quite well in compose, and I believe should be able to be implemented in the current app system (ie with the existing questions/templates etc)

It just needs to be done for the apps.

IP Aliases implemented that way may have implications on the host networking stack, however. You really should not have multiple IPs in the same network.

IP Aliases on the same interface are fine. Its when they’re on different interfaces, outside of a bond, that you have an issue.

The disambiguation is handled by the destination ip address field for inbound traffic, and the ARP table handles the IP<->MAC mapping.

1 Like

Thanks. I guess that the request may be closed as accepted and the votes released.

3 Likes