Port bindings at deployment manifest are not exposing ports

Question

We have a custom edge module in the deployment manifest but the port binds do not seem to be functioning. This syntax is similar to that of the blob storage module. Is this exposed port defined correctly with the following? Does another Docker setting require adjustment to expose port?

    "createOptions": {
        "HostConfig": {
            "LogConfig": {
                "Type": "json-file",
                "Config": {
                    "max-size": "10m",
                    "max-file": "3"
                }
            },
            "PortBindings": {
                "11009/tcp": [
                    {
                        "HostPort": "11009"
                    }
                ]
            }
        }
    }

Answer 1

Hello @Omar Navarro ,

adding Container Create options is always tricky :-)

It's good to know that "HostPort" is the port the container exposes on the host. This port has to be unique on the device, only one application (or container) can 'reserve' this port number.

I recently added a custom module on GitHub exposing UDP communication:

{  
    "ExposedPorts": {   
        "11001/udp":{}  
    },  
    "HostConfig": {  
        "PortBindings":{  
            "11001/udp":[   
                {  
                    "HostPort":"11001"  
                }  
            ]  
        }  
    }  
}  

Here, the internal port number is equal to the external (host) port number.