Container fails to scan channels - Native succeeds

[Velero]

NextPVR fails to scan and identify channels when running into a container. 

However, the same procedure succeeds when NextPVR runs natively.

I launch the scan from Settings > Devices > adapter0/frontend0 (DiBcom 7000PC) with fr-All.

I went through https://forums.nextpvr.com/showthread.php?tid=59458, to no avail.

Configuration:

• Linux NUC-8 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux
  
• Docker version 20.10.12, build e91ed57
  
• nextpvr/nextpvr_amd64table 5.2.6.220206
  

Installation as per https://github.com/sub3/NextPVR/wiki/Install-Docker

Code:

docker pull nextpvr/nextpvr_amd64:latest

docker run -d --name NextPVR --volume /home/user/NextPVR/config:/config --volume /home/user/NextPVR/records:/recordings --volume /home/user/NextPVR/buffer:/buffer --restart unless-stopped --publish 8866:8866 --device /dev/dvb:/dev/dvb --device /dev/dri:/dev/dri nextpvr/nextpvr_amd64:stable

Any hint of what I may doing wrong? Thank you!

[mvallevand]

If you can run natively to me running in docker makes no sense,

Upload your zipped logs and we can have a look for errors. Perhaps fr-All is different too?

Martin

[Velero]

Please find the log file attached.

[sub]

There is no obvious sign of errors there.

Does it appear to be scanning the correct frequencies? Checking that fr-All in the container is same as your native version. I don't specifically remember seeing a Docker user from France or Belgium, so there is the slightest possibility the tuning file is incorrect.

However, the same procedure succeeds when NextPVR runs natively.

The native instance is stopped, while trying to use the tuner from Docker? (it shouldn't need to, but just thinking possibilities)

[Velero]

Yes, during the tests with the container, the native instance is down and even removed.

finally, I have switched to the native instance and removed the container.