Error detecting HDHR devices with marklambert/nextpvr-ccextractor

[mvallevand]

Sorry I missed that If you can't get host mode working then you have a local issue, the x64 image itself works fine with the HDHR on Linux but I have never tested it on macOS.

Since you don't have any active channels mapped (your HDHR is disabled as not present) SD won't get anything.

I just noticed you aren't using the stock Docker but I doubt if that is the issue.

Martin

[SickBoy]

I think I have a lead:

Code:

akruse@radxa:/mnt/nvm/npvr/config/logs$ docker ps
CONTAINER ID   IMAGE                          COMMAND                  CREATED         STATUS                 PORTS                                                                                                                                                                      NAMES
83373dcefbe5   nextpvr/nextpvr_amd64:stable   "dotnet /app/NextPVR…"   4 minutes ago   Up 4 minutes           80/tcp, 0.0.0.0:8020-8030->8020-8030/udp, :::8020-8030->8020-8030/udp, 443/tcp, 0.0.0.0:16891->16891/udp, :::16891->16891/udp, 0.0.0.0:8866->8866/tcp, :::8866->8866/tcp   npvr
45e8b4290da5   ghcr.io/wg-easy/wg-easy        "docker-entrypoint.s…"   2 months ago    Up 5 hours (healthy)   0.0.0.0:51820->51820/udp, :::51820->51820/udp, 0.0.0.0:51821->51821/tcp, :::51821->51821/tcp                                                                               wg-easy
9ad3cdbcf5f2   pihole/pihole:latest           "/s6-init"               2 months ago    Up 5 hours (healthy)   0.0.0.0:53->53/tcp, :::53->53/tcp, 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:53->53/udp, :::443->443/tcp, :::53->53/udp, 67/udp                     pihole
akruse@radxa:/mnt/nvm/npvr/config/logs$

the nextpvr container is grabbing 80/tcp even though the run command isn't specifying it. Should it be doing that?

I shut down the Pihole container and everything works as expected, so I could alternately forward Pihole's internal port 80 to a different port (8080 or something), and maybe this is more of a docker issue than a NextPVR issue, but it is definitely unexpected behavior.

[mvallevand]

It is exposing 80 and 443 but it shouldn't be grabbing anything since there is nothing running on those ports on the docker (at least on sub's image)

Martin

[sub]

I've removed 80/443 for the next build.

[SickBoy]

I've removed 80/443 for the next build.

thanks sub!