March 30, 20215 yr I am struggling to work out why some info isn't showing up for some of my containers. eg. some containers are not showing any port mappings even though they are in use and working eg. looking at this container (I know it is stopped) shows the port mappings however this container doesn't show anything even though I do have port mappings defined (it is showing the volume mappings though) I have also attempted to add the missing Web UI for this container but whilst it is showing and included in the user template /boot/config/plugins/dockerMan/templates-user it doesn't show up as an option. I have recreated the container from the template and restarted docker but this doesn't seem to stick. Neither the port mapping nor the web UI menu item show up. What do I need to do to get this to work?
March 30, 20215 yr Because it's on a separate bridge and because the dockerfile the author created doesn't expose any ports. Nothing to worry about
March 30, 20215 yr Author 12 minutes ago, Squid said: Because it's on a separate bridge and because the dockerfile the author created doesn't expose any ports. Nothing to worry about It is not a worry just a slight annoyance. There is now a port exposed as I added this via unraid but this is being picked up from the image not unraid? (hence it is possible to add ports in Unraid and they won't appear in the GUI?) The bridge isn't an issue (see the top one, that has details). What about the Web UI though, that has to be unraid specific and I have updated the template to include a web UI address but this doesn't appear in the menu for the container.
March 30, 20215 yr 1 hour ago, jameson_uk said: hence it is possible to add ports in Unraid and they won't appear in the GUI?) Correct. Anything you add still works, but if the dockerfile doesn't reference them you won't see them. Basically lazy authors. The WebUI thing is also related, (but only when running on a custom bridge)
March 30, 20215 yr Author 51 minutes ago, Squid said: Correct. Anything you add still works, but if the dockerfile doesn't reference them you won't see them. Basically lazy authors. The WebUI thing is also related, (but only when running on a custom bridge) I had a play around with a few of my containers and see the EXPOSE in the Dockerfile controls which ports show up here. I would have thought it would be far more useful to see what ports are actually in use (I guess the main point of the "show docker allocations" is to avoid conflicts which would be dependant on showing the ports actually mapped not the ones advertised but I can live with that (It is just a bit annoying that you cannot see the IP or ports for these without going into the config. So the WebUI thing (which is nothing to do with Docker) doesn't work on anything other than the default bridge network? I am failing to see why this would be a limitation (from a technical viewpoint) as it is only IP / port which should still be able to resolve?
March 30, 20215 yr Community Expert 2 hours ago, jameson_uk said: So the WebUI thing (which is nothing to do with Docker) doesn't work on anything other than the default bridge network? Not correct
March 30, 20215 yr Yeah I over simplified so long as there is at least one port the system has mapped (even though its ignored) will bring up a webui
March 31, 20215 yr Author 22 hours ago, Squid said: Yeah I over simplified so long as there is at least one port the system has mapped (even though its ignored) will bring up a webui Just to be clear, you mean exposed in image rather than mapped right?
March 31, 20215 yr Yes. IIRC It's been quite a while since I've looked at this. The not displaying only really affects HOST / Custom networks.
Archived
This topic is now archived and is closed to further replies.