I've been having some issues for a while now when it comes to port mappings for Docker. Not with any one container, but usually most of them and all different containers.

 

I've found that Unraid isn't using the -p parameter at all, regardless of it existing withing the UI itself.

 

As you can see below screenshot, I have the host set to port 8888, however, in the command that is run it is not using the -p parameter at all.

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='H5AI' --net='br1' --ip='192.168.1.243' --log-opt max-size='50m' --log-opt max-file='3' -e TZ="Australia/Brisbane" -e HOST_OS="Unraid" -e 'TCP_PORT_80'='8888' -v '/mnt/user/isos/':'/var/www':'rw' -v '/mnt/user/appdata/H5AI':'/config':'rw' 'smdion/docker-h5ai' 

 

Below is also the Template for this container, which looks fine imho

<?xml version="1.0"?>
<Container version="2">
  <Name>H5AI</Name>
  <Repository>smdion/docker-h5ai</Repository>
  <Registry>https://registry.hub.docker.com/u/smdion/docker-h5ai/</Registry>
  <Network>br1</Network>
  <MyIP>192.168.1.243</MyIP>
  <Shell>sh</Shell>
  <Privileged>false</Privileged>
  <Support>http://lime-technology.com/forum/index.php?topic=34009.0</Support>
  <Project/>
  <Overview>
    H5AI is a modern web server index. This docker image makes it trivially easy to spin up a webserver and start sharing your files through the web.[br][br]
    [b][span style='color: #E80000;']Directions:[/span][/b][br]
    [b]/config[/b] : this path is used to store the configuration H5AI.[br]
    [b]/var/www[/b] : this path is that will be shared via a web index by H5AI.[br]
  </Overview>
  <Category>Cloud: Network:Web</Category>
  <WebUI/>
  <TemplateURL>https://raw.githubusercontent.com/smdion/docker-containers/templates/smdion-repo/H5AI.xml</TemplateURL>
  <Icon>http://i.imgur.com/SxqiOrd.png</Icon>
  <ExtraParams/>
  <PostArgs/>
  <CPUset/>
  <DateInstalled>1574299393</DateInstalled>
  <DonateText/>
  <DonateLink/>
  <Description>
    H5AI is a modern web server index. This docker image makes it trivially easy to spin up a webserver and start sharing your files through the web.[br][br]
    [b][span style='color: #E80000;']Directions:[/span][/b][br]
    [b]/config[/b] : this path is used to store the configuration H5AI.[br]
    [b]/var/www[/b] : this path is that will be shared via a web index by H5AI.[br]
  </Description>
  <Networking>
    <Mode>br1</Mode>
    <Publish>
      <Port>
        <HostPort>8888</HostPort>
        <ContainerPort>80</ContainerPort>
        <Protocol>tcp</Protocol>
      </Port>
    </Publish>
  </Networking>
  <Data>
    <Volume>
      <HostDir>/mnt/user/isos/</HostDir>
      <ContainerDir>/var/www</ContainerDir>
      <Mode>rw</Mode>
    </Volume>
    <Volume>
      <HostDir>/mnt/user/appdata/H5AI</HostDir>
      <ContainerDir>/config</ContainerDir>
      <Mode>rw</Mode>
    </Volume>
  </Data>
  <Environment/>
  <Labels/>
  <Config Name="Host Port 1" Target="80" Default="8888" Mode="tcp" Description="Container Port: 80" Type="Port" Display="always" Required="true" Mask="false">8888</Config>
  <Config Name="Host Path 2" Target="/var/www" Default="" Mode="rw" Description="Container Path: /var/www" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/isos/</Config>
  <Config Name="AppData Config Path" Target="/config" Default="/mnt/user/appdata/H5AI" Mode="rw" Description="Container Path: /config" Type="Path" Display="advanced-hide" Required="true" Mask="false">/mnt/user/appdata/H5AI</Config>
</Container>

 

Port mappings are only relevant when you're using Bridge mode for network type.  For anything else the container can uses whatever ports it decides

Just now, Squid said:

Port mappings are only relevant when you're using Bridge mode for network type.  For anything else the container can uses whatever ports it decides

You know what? Now that you say that it makes perfect sense! Duh! Thank you @Squid

 

Here I was thinking it was a bug. 😳