Docker options

[tom_tav]

Hello!

First steps into nextpvr it raised some questions:

1. When starting the container in host mode .... it seems the container doesnt get a valid ip via DHCP. And to set it manually for testing is a little bit difficult with the missing ipaddr tool. Do i miss something? (Docker is running on OS X)

2. The "--env SATIP_DEVICES=xxx" option. I found some hints here but it is not in the docs. In the forum there is one usage of "--env SATIP_DEVICES=http://192.168.178.20/octoserve/octonet.xml" ... but what exactly is it expecting? Is it just a link to the receivers channel list? The m3u style request string? ... The ffmpeg -i option params? 

3. The extras-*.xml file: The documentation is refering to put the file into the "data" dir, which is a little bit misleading because all the docker related docs is not mentioning data. In fact it is loaded from /config. Also a hint to properly format XML ( "&" -> "&") would be good, many receiver strings do have these characters inside the request strings

These are just some points i stumbled over, the main problem and one bug i did encounter i will open another thread to nut clutter this one

Cant wait to get nextpvr working and to see what it can

[mvallevand]

I think you need bridge mode for SAT>IP because of the ephemeral port RTSP uses. You can try the HOST_IP environment variable to report

Many SATP>IP device have a satdesc.xml file if discovery doesn't find the device. I don't think it helps 100% with using host mode though.

Since extras.xml is an XML file by definition it needs to follow the XML spec which is more than the just encoding.

Martin