TrueNAS SCALE 24.10-BETA.1 is Now Available!

[Stux]

@Stux

Another approach is to use an ip alias on the truenas side, you can then bind to that on the docker side, no routing issues, but the issue is that TrueNAS likes to bind most of services to 0.0.0.0 which is all ips.

Vote for this feature request if you want to be able to bind ports to IPs in apps, and not just compose

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,…