Chilipants

Disabling Host access to custom networks on docker settings should suffice... it's not necessary for proxynet. I had mine enabled for some reason or another ( testing at some point ) and forgot to disable and it was the sole cause of my macvlan call traces and lockups. Disabling it has ceased all macvlan problems for me. This was addressed earlier in this thread by kaiguy and bonienl. Seems nic driver related since different cards have different stabilities when host access is enabled.

Just installed 6.9.2 today, macvlan kernel panic within 4 hours. I used to get frequent macvlan call traces and hard lockups when I had an intel 10gbit card installed on 6.8.3 and up, until I replaced it with a dual 1 gbit intel card. 6.9.1 had no macvlan traces or lockups. Diagnostics attached... tower-diagnostics-20210410-2213.zip

I installed this docker and was unable to get the dvr service to work. Manual recording worked fine. Installing the miniDLNA docker and then using the NAS install from the windows hdhomerun utility enabled the dvr service properly, however, the service needs to be restarted at every reboot of the miniDLNA docker. After a bit of digging, I found that supervisord could be used within the miniDLNA docker. Start the miniDLNA console and add : [program:hdhomerun_record] command = /media/hdhomerun_record foreground --conf = /media/hdhomerun.conf autorestart = False user = nobody umask = 000 to a file called hdhomerun_record.conf in /etc/supervisor/conf.d/ I used vi to do this. I had to delete my previous record tasks and re-add them after getting miniDLNA installed and working. Not sure if a miniDLNA docker update will wipe this or not...perhaps a path setting in docker config could be set to preserve this file if so?