Ports

The default ports that the Norsk Media Container uses are as follows:

If you are running with Docker Networking, you can obviously map these ports to whatever you want, see the Docker documentation for details on publishing ports.

If you are running with Host Networking then you can override these ports using the startupConfiguration.adoc. A typical reason for doing this would be to run multiple Norsk Media instances on the same host. Note that when in host networking you cannot configure Norsk to use privileged ports (i.e. ports below 1024). We intentionally do not allow Norsk to run as root (or with any other form of elevated permissions), so it will not have access to listen on those ports.

If you want to access Norsk via privileged ports whilst in host networking, we would recommend the use of an industry standard reverse proxy such as Nginx or cloud load balancers such as Amazon’s ALB. We would also recommend this approach to terminate TLS connections should you wish to provide e.g. HTTPS access to streams.

On macOs, although host networking is nominally supported by docker, in practice is is not practical for Norsk Media. On macOs, Docker Desktop spins up a local Linux virtual machine on which to run the containers. If you run with host networking, it is this VM that is the host, not your Mac. The IP address of that machine is deliberately kept well hidden, meaning that you are unlikely to be able to get media either into or out of your container.