Bind a container in 24.10

[accrocchio96]

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?

[Stux]

You need to add the IP as an IP Alias on the network interface in network settings.

Then if you want to use any ports that the middleware uses, eg 80/443,make sure that the middleware is not binding to that IP.

You need to use a custom compose file via cli/dockge or portainer if you want to bind to a specific ip.

TrueNAS Scale: Migrating Sandboxes to Docker in Electric Eel // Compose, Dockge & Jailmaker

Alternatively, you can use macvlan with docker. This still requires custom compose.

[Stux]

BTW, this is a feature request to add support for binding apps to specific IPs

Add "Bind IP Address" to app "port" selection UIs

There is no way to bind an app’s port mapping to a specific IP address in Electric Eel beta. If an IP Alias is added to an interface, then that IP Alias can be used when configuring port mapping in raw docker-compose. eg: ports: - 192.168.0.40:80:80 Will bind port 80 on the host’s 192.168.0.40 IP alias to port 80 in the container. Of course, for the above to work, the TrueNAS UI must first be bound to a specific IP instead of 0.0.0.0 Similarly, docker will bind to 0.0.0.0 by default,…

[accrocchio96]

I did it (not the last macvlan alternative) and that is what I did in first message (probably written too fast).
Now rechecking that I notice that now it works as we thought.
Probably yesterday there was a sort of cache.

Thanks for the feature request! And for your job!