- Solved
- Minor
Old bug, but its never been addressed.
If a container doesn't have a port exposed in its dockerfile, the Unraid Docker page isn't able to determine its IP address.

This is especially problematic for containers using custom networks that don't need ports exposed to function.
Adding a mapped port in the unraid template does not make the ip address appear either.
Docker itself has no problem returning the addresses missing when querying docker
docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container_name_or_id
This seems to be an Unraid implementation limitation due to the requirement to get and display exposed port(s).
My suggested fix is that when using custom networks, containers should only attempt to show the IP, as published ports are largely irrelevant in this case.