I have quite a few dockers and run them with a Bridge interface. Most of them are just fine, but recently - and i dont know why - when i add a container and put it on the bridge network, the port mappings just shows blank. The docker is still functioning fine and i can reach it on my assigned IP address, but i do not see the port mappings on the Docker page. 

 

 

1 hour ago, prytzen said:

I have quite a few dockers and run them with a Bridge interface. Most of them are just fine, but recently - and i dont know why - when i add a container and put it on the bridge network, the port mappings just shows blank. The docker is still functioning fine and i can reach it on my assigned IP address, but i do not see the port mappings on the Docker page. 

 

 

 

custom br0 is using ipvlan / macvlan which doen't do docker nat port mappings. if the container has a server and port running that port is open and avilable at that IP.
 

 

review:

 

 

12 hours ago, bmartino1 said:

 

custom br0 is using ipvlan / macvlan which doen't do docker nat port mappings. if the container has a server and port running that port is open and avilable at that IP.
 

 

Thanks. I believe i understand this portion of it. I have all of my Dockers setup with BR0 so I can keep them exposed on a specific VLAN and they have their own IP address. The port mappings are just 1:1 at that point, so nothing changes. The issue, and maybe I didn't make that clear, was that there is just no information showing up on the page about the IP address or port as my other docker containers do, like below

 

1 hour ago, prytzen said:

Thanks. I believe i understand this portion of it. I have all of my Dockers setup with BR0 so I can keep them exposed on a specific VLAN and they have their own IP address. The port mappings are just 1:1 at that point, so nothing changes. The issue, and maybe I didn't make that clear, was that there is just no information showing up on the page about the IP address or port as my other docker containers do, like below

 

That because this being read from the template. if a template port is added, it will show there same with the mounts at the right.

This is not activity reading or reporting what the docker has mounted nor port accessible as live data...

 

in unraid v7 you will see port set to "all"

 

example:

 

while older unraid will see ports reported via the template:

in your case plex:

the template has:

and is displaying as such per the web page code...

 

since its in br0 custom macvlan/ipvlan its actually doing all ports the docker web ui has no other check and way to show current active...

This is why the other br0 docker doesn't show any ports. the template doesn't have a port mapping and wouldn't use it regardless.

 

I believe i understand what you are saying. looking at my RustDesk container, it shows that there are Ports defined in the template, but nothing shows up on the Docker page. So I still think something is up and not displaying correctly. I do ultimately need to update to v7 so I can guess I can attempt that and see if the behavior changes at all. 

 

 

 

I think if you set your create the docker "rustdesk" orginal as a docker bridge it will show the port ports, then stop and edit it back to custom br0 it might stick due to the webstie generate metadata. Usualy I use docker inspect and other termla commands to confirm and verify.

 

has more to do with issues with the command docker port cli
https://docs.docker.com/reference/cli/docker/container/port/

the emhttp docker web ui page is a bit weird. 

https://github.com/unraid/webgui/blob/master/emhttp/plugins/dynamix.docker.manager/DockerContainers.page

 

its hard to say with the older version of when and what gets read.