OctopusNet not visible in docker in Synology

[marcodalli]

Hi,
I'm struggling to make NextPVR work inside docker running on a Synology NAS.
I've setup the container both using host network or bridge (adding the SATIP_DEVICES with the URL of my OctopusNet), but I can find no devices.
Also, if I try to import a m3u playlist, nothing happens, so I suspect there's something wrong with my setup.

In the logs I see

Code:

2021-07-13 22:47:10.596    [DEBUG][10]    address: 10.1.0.2
2021-07-13 22:47:10.608    [ERROR][10]    Unexpected error getting IP address: System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (00000005, 0xFFFDFFFF): Name or service not known
   at System.Net.Dns.InternalGetHostByName(String hostName)
   at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
   at NShared.LocatorService.DetermineIPAddress()

where 10.1.0.2 is the NAS's IP.

What am I doing wrong?

Thank you,
Marco

[marcodalli]

Ok, that's very weird... I just installed NextPVR in my Windows machine and it correctly detected the SAT>IP tuner.
I then copied the config folder from C:\Users\Public\NPVR-data to the share on the Synology and now it's there, alongside my physical tuners connected to my PC (which I deleted from the docker instance).
It's even scanning...
Next step: tell NextPVR to use the internal CI on the OctopusNet...

[mvallevand]

A few things.

1. It is /buffer not /buffering
2. I don't see the ENV variable for SAT_IP devices
3. Are files being created in Software/NextPVR/config, you need to create it before running? Your logs don't match the statement of trying different tests.

Martin

[marcodalli]

Hi Martin,
thanks for the quick reply.
1. Sorry, I mistyped it, now it's correct
2. In this case I was trying with host network, but in all cases the device did not show up. What resolved it for me was setting it up on a Windows machine and then copy the copy over to the docker install...
3. Yes, they are created automatically during first run. The logs don't match because I cleaned them before reinstalling docker, thinking that something was left behind in the config / DB (this is prior to importing the config from Windows).

Marco