mherger wrote: > > > I don't know the helper application, but it is no problem to make an > > application available via network - you can just forward the relevant > > ports to the container. That's what happens with the LMS image too: > > forwarding of port 9000 allows the website to be reachable from > outside > > the docker host.[/color] > > But I'd have to modify the image, wouldn't I? It's not something Joe > Average would be doing? >
Theres a `--publish` option to `docker run` to tell it which ports you want to forward to the container, or a `--publish-all` option to tell it to forward all ports described in the image. The trouble that Michael correctly identifies is that an LMS image wouldnt know about all of the ports that LMS plugins might want, making the `--publish-all` option not useful. Further, the `--publish` option has to be supplied -outside- the container, meaning that a plugin could not automatically open ports, there'd need to be manual intervention from the user. One can imagine publishing an LMS+Spotify container image, where the Spotify plugin had been layered on top of the base LMS image. However, this wouldnt be scalable to all plugins, and would remove the possibility of managing plugins from within LMS. ------------------------------------------------------------------------ mavit's Profile: http://forums.slimdevices.com/member.php?userid=10203 View this thread: http://forums.slimdevices.com/showthread.php?t=111828
_______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
