<div dir="ltr">Trying to setup mythtv-backend in a docker container.  However, running into issues trying to get the networking setup correctly with the hdhomerun tuner card. Anyone got this to work? Basically, i can't seem to get the bridge working correctly, so my hdhomerun network tuner doesn't work. I don't know enough about docker's internal networking scheme to figure it out...<div><br></div><div><br></div><div><a href="https://github.com/jgoerzen/docker-mythtv">https://github.com/jgoerzen/docker-mythtv</a><br></div><div><br></div><div>Author noted this:</div><div>(pasted from his site above)</div><div><br></div><div><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px">Also, if you use a capture device like the HDHomeRun which communicates back to MythTV via random UDP ports, it can be just about impossible to make things work with the standard docker port forwarding.</p><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px">However, there are some workarounds.</p><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px">You can:</p><ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px"><li style="box-sizing:border-box">Use NAT reflection on your firewall to forward packets back in to your network.</li><li style="box-sizing:border-box;margin-top:0.25em"><a href="https://developer.ibm.com/recipes/tutorials/bridge-the-docker-containers-to-external-network/" style="box-sizing:border-box;background-color:transparent;color:rgb(3,102,214);text-decoration-line:none">Bridge your Docker containers to the network</a><ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:0px"><li style="box-sizing:border-box">An example: <code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;padding:0.2em 0px;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:3px">docker network create --driver=bridge --ip-range=<a href="http://192.168.0.192/29">192.168.0.192/29</a> --subnet=<a href="http://192.168.0.0/24">192.168.0.0/24</a> --aux-address "DefaultGatewayIPv4=192.168.0.1" -o "<a href="http://com.docker.network.bridge.name">com.docker.network.bridge.name</a>=brlan1" brlan1</code></li><li style="box-sizing:border-box;margin-top:0.25em">After that, you can add <code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;padding:0.2em 0px;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:3px">network=brlan1 --ip=192.168.0.193</code> do your <code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;padding:0.2em 0px;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:3px">docker run</code>, and you do not need any <code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;padding:0.2em 0px;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:3px">-p</code>because it will be directly accessible on the new IP.</li></ul></li><li style="box-sizing:border-box;margin-top:0.25em">Add egress iptables rules to your frontends</li><li style="box-sizing:border-box;margin-top:0.25em">You can set the BackendServerIP and MasterServerIP to the "visible" IP of the backend (will probably have to do this via mysql). mythbackend will fail to bind to a visible IP, but a userland redirector like <code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;padding:0.2em 0px;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:3px">redir</code> may do the trick.</li></ul><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px">I tried adding <code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation Mono",Menlo,Courier,monospace;font-size:13.6px;padding:0.2em 0px;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:3px">-O BackendServerIP=blah -O MasterServerIP=blah</code> to my mythfrontend command line. That let it boot, but wasn't sufficient for streaming.</p></div></div>