NextPVR Forums - Docker arm32v7

Help with upgrade to latest arm32v7 container

Tue, 02 Sep 2025 19:08:06 +0000

I've been happily using an old arm32v7 image, version 6.1.5.231022, for years on a Raspberry Pi 4. Works fine for my purposes.

Today I tried to update to the latest image, version 7.0.2.250621. The only thing I changed was to pull the new image from Docker Hub; I kept the rest of the configuration the same. To me it now "feels" like I've lost communication with my tuner, which is a USB-connected single tuner Hauppauge 950.

For this device, the docker run command specifies:

Code:
--device /dev/dvb:/dev/dvb

but perhaps this is not correct or sufficient for the new version of NextPVR? From dmesg I see the tuner device being found and being initialized with microcode on /dev/dvb, so that's good.

On the plus side, the web interface for the new version does come up, I can log into it, and I see my device list and channel map as before. EPG fetching also works. But there's no evidence that NextPVR is talking with the tuner (channel scan, manual program request yield either "Transcoder exited" or "There is no tuner available").

If I simply switch back to the old image (with docker tag) and reboot, everything works again. I'd sure like to have the benefits of the newest NextPVR version if possible - any suggestions? Thanks!

Daylight saving time change shifted my scheduled recording times

Mon, 31 Mar 2025 09:57:53 +0000

Hello,

This week-end, where I live, we set clocks forward by one hour (daylight savings). The time change happened Sunday morning at 2:00am: When it used to be 2:00am, it is now 3:00am.
I had a program recording scheduled Sunday night (yesterday, after the time shift), at 9:10pm. Today, I noticed the recording started only an hour later than expected (10:10pm).

I tried to understand what may have caused it. I remembered the daylight saving time, and thought this may be related. I took a look at the TV Guide tab of the web interface of NextPVR: the vertical line of the time indicator properly indicates the current time (but I have no idea if this was the case yesterday).

However, I headed over to the "Scheduler" tab, and noticed that the start times of all my scheduled recurring recordings are all:

set back by an hour in the "Pending" list (e.g. if a recording used to start at 9:05pm, it now reads "10:05pm")
set forward by an hour in the "Recurring" list (e.g. if a recording used to start at 9:05pm, it now reads "8:05pm")

As a side note, I tested further: After scheduling a new recording by pressing the (+) icon, the new recording list item displays:

the correct start time in the "Pending" list
the wrong start time in the "Recurring" list (time is set back by an hour, now)

The clock of my NAS that hosts my NextPVR Docker container is updated properly and follows the daylight saving time properly (just confirmed).
I restarted by docker container, updated the Scheduler web page (Ctrl-F5), and the start times are still offset...
Have you ever faced this type of issue? Do you know what may be causing it?

Thank you.

Manually scanning the DVB EPG while a recording is in progress causes it to abort

Wed, 26 Mar 2025 23:19:32 +0000

Hello,

I'm using version: 7.0.1.241229 with a Docker arm32v7. I am able to reproduce a problem here. If a recording is in progress and if I click the "Update EPG" button in the settings, as soon as the progress hits a channel that is set to a DVB EPG, this aborts the recording. It doesn't seem the XMLTV EPG format causes any problem, from my tests so far. I have attached the log files.

Kind regards.

logs-20250326-2313.zip (Size: 740.04 KB / Downloads: 1)

Update arm32v7 image on Docker Hub

Sun, 10 Nov 2024 15:06:22 +0000

I've got several older Pi's that use this flavor of NextPVR. Will the image on Docker Hub be updated to the latest rev 7.0.0.241105 as has been done for the amd64 image? The fixes and improvements list looks long and wonderful, and I'm hoping my older boxes will be able to migrate to it. Thanks.

Always stops working after some time (2)

Tue, 15 Oct 2024 10:17:15 +0000

Hello,

I was reading the forum messages, and it seems I have the same problem as this user. I scheduled weekly recordings that are supposed to last 2h, but they actually last no more than 5 minutes. I always end up throwing them away, I only have the commercials at the beginning of the TV program, the TV program itself doesn't even begin when the recording is aborted. Here is the section of the log file that I think is relevant, although I don't understand much. From my understanding the NAS receives 200MB of data every ten seconds? This is huge... How is it possible, to begin with? (it's a simple 1080i h.264 TV stream...).

Code:
2024-10-13 21:14:15.314 [DEBUG][144] Have received 198136960 bytes from rtp source

2024-10-13 21:14:25.414 [DEBUG][144] Have received 198136960 bytes from rtp source

2024-10-13 21:14:35.514 [DEBUG][144] Have received 198136960 bytes from rtp source

2024-10-13 21:14:45.614 [DEBUG][144] Have received 198136960 bytes from rtp source

2024-10-13 21:14:55.714 [DEBUG][144] Have received 198136960 bytes from rtp source

2024-10-13 21:15:00.125 [DEBUG][11] Stopping recording (902 on 21). Past end time of recording. 257

2024-10-13 21:15:00.493 [DEBUG][11] StopStream(257)

2024-10-13 21:15:00.493 [DEBUG][11] StopStream handle: 257

2024-10-13 21:15:00.512 [DEBUG][11] Closing TSWriter....: /recordings/Manual Recordings/FELA_20241013_19102110.ts

2024-10-13 21:15:00.523 [ERROR][11] writer.Close() did not complete in a timely fashion

2024-10-13 21:15:00.523 [DEBUG][11] Close@2

2024-10-13 21:15:00.523 [DEBUG][11] Closing mapAccessor

2024-10-13 21:15:00.576 [DEBUG][11] Closing mapMMF

2024-10-13 21:15:00.576 [DEBUG][11] Closing mapFileStream

2024-10-13 21:15:00.577 [DEBUG][11] deleting /recordings/Manual Recordings/ABC_20241013_19102110.ts.map

2024-10-13 21:15:00.591 [DEBUG][94] Reached end of in-progress recording. Dropping connection.

2024-10-13 21:15:00.595 [DEBUG][11] Close@exit

2024-10-13 21:15:00.596 [DEBUG][11] StopStream@exit

2024-10-13 21:15:00.611 [DEBUG][94] Sent total of 198133200 bytes

2024-10-13 21:15:00.764 [DEBUG][144] Shutting down RTP input stream

2024-10-13 21:15:00.764 [DEBUG][11] stopping legacy hdhr stream

2024-10-13 21:15:01.922 [DEBUG][11] stopping graph

2024-10-13 21:15:01.922 [DEBUG][11] destroying graph

2024-10-13 21:15:01.922 [INFO][11] Stopped

2024-10-13 21:15:02.237 [DEBUG][11] StoreMetaData@exit

2024-10-13 21:15:03.740 [DEBUG][11] PowerManagement AllowSleep (needs implementation)

2024-10-13 21:15:03.740 [DEBUG][11] No longer active

2024-10-13 21:15:04.403 [DEBUG][135] timing closed

More info: I'm using v.6.1.5.231022, in a Docker image, on a QNAP TS-131P NAS (arm32). I have plenty of free space on this NAS.
I have restarted Docker several times, with no improvements.
I am able to record from my computer using the same Ethernet DVB-T tuner for hours trouble-free using DVBViewer (a separate Windows application).
Do you know what may be aborting my recordings?
Thank you!

Note: I'm getting an error message on the forum reporting too many MySQL connections.

NextPVR/Docker on a RPi 5

Sun, 31 Dec 2023 16:28:34 +0000

For years I've happily run NextPVR/Docker on an RPi 4, and just having received a new RPi 5, I've tried to port over my working configuration. I think I've copied and configured all the pieces, but the container exits almost immediately after it starts. If I allow it to auto-restart, it will repeat the start/exit activity forever. There are a LOT of differences between the new RPi 5 runtime environment and the old one - machine architecture, OS version, package versions. Two questions - (1) have folks gotten the current nextpvr/nextpvr_arm32v7:latest container to work on an RPi 5 with the latest version of Raspberry Pi OS (64)? And (2) is there a logfile that I can view inside the container (or map to a directory on the host) that I can maybe see what's causing the exit and debug it further?

One additional clue is that docker-proxy is not starting up, but that might be because the container exits so quickly. I do see the Docker bridge network in the routing table.

Thanks!

Always stops working after some time

Thu, 02 Nov 2023 19:52:36 +0000

Hello there,

I migrated my installation to a docker environment recently. After some tweaks I got it working almost immediately and was able to record and play Live TV, so I scheduled some recordings. After some days I logged in and saw that all recordings failed with note "[Failed: The operation has timed out.]". I switched to Live TV and it did not work, so I restarted the container and after that everything worked again. I have now repeated this process multiple times. I attached the most recent log.

Best,
Philipp

log.zip (Size: 765.56 KB / Downloads: 2)

Can't stream TV channels

Fri, 20 Oct 2023 11:39:23 +0000

Hello,

I installed a Docker container with NextPVR on my QNAP NAS. I am able to record TV channels but I am unable to watch any TV channel : I get an error message at the bottom of the screen in red: "Streaming Failed (transcoder exited)". Here's the log information. I use a SiliconDust HDHomeRun dual-tuner. Could you help me, please?

nextpvr.log.zip (Size: 5.76 KB / Downloads: 1)

Errors from pvr.nextpvr in Kodi

Wed, 09 Aug 2023 16:23:13 +0000

Hi Folks

i am running CoreELEC latest stable version 20.2 Nexus on an Odroid N2+.

i run NextPVR docker container and am running Version: 6.1.4.230625 . i am using latest NextPVR client from CoreELEC repo v8.2.0.

i have migrated Kodi to run on SSD from one of the USB ports, it runs Maria DB considerably faster than the SD did, however, i get random crashes, even after several clean installs.

i am going to take this up on the CoreELE forum. i see the below errors about GetChannelGroupMembers repeating often in Kodi log. I am pretty sure this is not related to my issues and not an issue at all, as the same error was there when i was running on SD without any crashes, but for sure the CoreELEC guys will ask me about them. Is this expected? Does anyone know what causes the below, or see similar errors in Kodi logs?

2023-08-09 17:06:53.073 T:4117 info : PVR Manager: Starting
2023-08-09 17:07:13.973 T:4395 error : GetChannelGroupMembers: Add-on 'pvr.nextpvr' returned an error: server error
2023-08-09 17:07:24.051 T:4395 info : Skipped 73 duplicate messages..
2023-08-09 17:07:24.051 T:4395 error : GetChannelGroupMembers: Add-on 'pvr.nextpvr' returned an error: server error
2023-08-09 17:07:27.056 T:4227 info : Skipped 14 duplicate messages..
2023-08-09 17:07:41.620 T:4395 info : PVR Manager: Started
2023-08-09 17:07:55.736 T:4395 error : GetChannelGroupMembers: Add-on 'pvr.nextpvr' returned an error: server error
2023-08-09 17:08:05.755 T:4395 info : Skipped 81 duplicate messages..
2023-08-09 17:08:05.755 T:4395 error : GetChannelGroupMembers: Add-on 'pvr.nextpvr' returned an error: server error
2023-08-09 17:08:18.321 T:4395 info : Skipped 6 duplicate messages..
2023-08-09 17:08:18.321 T:4395 info : PVR Manager: Starting cleanup of cached images.
2023-08-09 17:08:23.694 T:3588 info : Samba is idle. Closing the remaining connections
2023-08-09 17:08:25.712 T:4395 info : PVR Manager: Cleaned up 0 cached images.

Thanks!

Add permission fix for dvb devices to docker image?

Thu, 03 Nov 2022 23:13:15 +0000

Could this permission fix be added to the docker image for dvb devices? It's a commit from the linuxserver.io images but the script should theoretically work for this docker image too

(Permission fix) https://github.com/linuxserver/docker-tvheadend/pull/137/files

Currently I have a systemd oneshot service chowning /dev/dvb recursively to the user (it runs as an ExecStartPre action when I start the service for my container) that my podman containers run under (while I am using podman most stuff is interchangeable anyway so it doesn't make a difference really which one you are using), but this would be nice to make sure it works without external intervention for userspace containers

Almost there, but no Scan button

Wed, 22 Dec 2021 19:41:27 +0000

I was happy to learn that there's a Dockerized NextPVR for the Raspberry Pi4. I have configured things and I'm almost there, lacking only the "Scan" button on my device page. Here are my configuration details:

RPi 4 , Raspbian 11 Bullseye
NextPVR Docker container arm32v7stable, version 5.2.3.211114
Hauppauge WinTV HVR 950 USB tuner
HD Homerun HDHR3-CC (3 tuners)
Guide information from SchedulesDirect

When the Pi boots there's a lot in the dmesg relating to the HVR 950. There was a complaint about missing firmware, and I followed other instructions on the web to furnish the xc3028-v27.fw file. I ran the container using the docker-run command given on the Docker install page, and I was able to bring up the web UI on port 8866. Under Settings/Devices I see my one "IPTV device" along with my three HD Homerun tuners. But there's no "Scan" for the HVR 950, only "Import/m3u" and "Import/XC" (and I'm not sure how to use those options).

As a side-note, if I decide to use one of the HDHomerun tuners, it will Scan, and NextPVR accumulates a large channel list. And from there I can tune any of those channels fine. That's great, but for this exercise I'm interested in the HVR 950, not the HDHomerun's.

Also, I use this same Hauppauge tuner on a Windows copy of NextPVR, and it works fine there, including a Scan button. It required a Windows driver download from Hauppauge to work correctly.

Lastly, I was a little surprised that the docker-run command does not include any --device clauses that would jam the path of my USB tuner into the container.

Thanks for any advice!

channel group sort settings not respected

Tue, 21 Sep 2021 08:15:33 +0000

Hi Folks,

i recently did a fresh install of corelec and then docker and npvr. i am running nvpr 5.2.0.210912 .

i found the value in config.xml false does not appear to be repected and all my groups in Kodi show in alphabetical order, rather then the order i have configured in my M3u.

i tried deleting Kodi epg and tvdb and rebooting a few times, and also a couple more completely fresh installs of corelelc (latest ng nightly and also latest ng stable) but no change.

has something changed in this image relating to this setting - more i need to do perhaps?

previously i was on an older 5.1 docker version of npvr and the setting was working fine, i also have npvr on my win 10 PC (5.1.1.210329) and if i point my kodi box to that as back end, and delete kodi epg and tvdb files, the groups show in kodi in order i set in my m3u, not alphabetical as i see in latest docker image.

Thanks

Docker image for WD MYCLOUD OS 5

Mon, 22 Mar 2021 16:31:56 +0000

Hi,

Thank you for your hard work, really appreciated,

So, heres my situation: i currently used nextpvr on RPI 4 using raspbian without any problems.

But my idea is to uninstall nextpvr from the RPI and installed it on my WD NAS,

I currently have Docker installed on my NAS running two container without problem,

But when i install de container with this image found on Docker Hub: https://hub.docker.com/r/nextpvr/nextpvr_arm32v7

Container create succesfully but stop immediatly without any logs... strange

My NAS infos:

OS: MyCloud OS 5

Hardware:
processor : 0
model name : ARMv7 Processor rev 1 (v7l)
BogoMIPS : 1600.00
Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x4
CPU part : 0xc09
CPU revision : 1

So, any ideas are welcomes,

Thank you!

EPG Update on start up

Mon, 15 Feb 2021 12:05:40 +0000

Hi Folks,

i am running nextpvr in a docker install using latest image from December, and power my box using usb from my TV, so the box is only on when the TV is on. this leads to no EPG often when i turn on, and i need to manually update or wait for the next scheduled epg update run.

is it possible to force epg to update (xml url for iptv channels) when nextpvr starts using poststartup.sh and placing in the scripts folder?

if yes, what would i need to put in that file?

fyi i am using matrix RC running in CoreElec, and from what i read when EPG updates in NextPVR, it forces Kodi to update from NextPvr, and this is new for Matrix, so hoping a simple script to update on start will have my EPG populated well in an automated fashion shortly after the box is up and running....

Thanks

IPTV unusable on latest docker image

Tue, 08 Dec 2020 16:59:25 +0000

Hi Folks,

is anyone having issue with IPTV following the last image 25th Oct v5.0.9.201026?

my docker boxes running latest CE are totally unusable, i get the TV picture up after quite a pause, then it freezes and every 10 -15 seconds it might move for a second or two then freeze again, this is happening on both SD and HD channels. Switching to IPTV Simple client on the same box plays the channels very smooth.

i also have the same version of NextPVR backed on my windows PC, and that plays smooth on windows, and also on my docker boxes if i point the NextPVR client to the PC instead of the local docker install, ive noticed a small stutter when i launch a channel from PC back-end that was rare previously but after that it is very smooth.

nothing jumps out at me in the logs from the docker boxes (i have attached a log)

prior to this latest image all had been working great on my CE /docker boxes..

i have docker boxes with their own reduced channel lists in each of my bedrooms, and another box in my lounge that connects to the back end on my PC with all channels. the docker boxes are a mix of AMLogic s905x, s905x3 and S912 and all appear to be effected

Thanks!

nrecord.zip (Size: 74.45 KB / Downloads: 2)