Yoshiofthewire

No, that is normal. And by normal, I mean doesn't hurt anything and I have no idea what I am doing.

So, it should now update to the latest version. I was trying to not manually have to unpack and upload every build....gives up.

I replaced the url with a short url that should fix it. https://goo.gl/SMd5ne

If you have installed the DVR somewhere else, there really is no setup. If you haven't you do need to configure your HDHomerun Tuner. Your configuration will survive the complete deletion of the docker and container. I am using an HDHomeRun Prime on Verizon. I can record and watch anything that is not DRMed. I can't watch any channel that has DRM. YMMV So, I can watch anything that is not FX, FXX, Fox Sports 1 (See a pattern). I don't have any premium channels. When I make changes, I do so to the live install .. because I have no idea what I am doing. I broke the install for about an hour yesterday. Please delete the docker container and file and reinstall. A reinstall is working for me this morning.

I think the docker keeps trying to start HDHomerun DVR ... after it has already started. So, it should be running OK. Mine has been up for a week without issue, that I know of. That said I think there are only like maybe 4 people running this, so if there was some edge case bug... That said, it looks like everything related to this is on the SiliconDust servers, so there isn't a lot to mess up.

FYI: It appears that even if you delete the container you will not lose your recording schedule. (Updated 1st post to match forum)

You need to either be a Kickstarter backer, or buy an early access license from their site of $60. When it is released it will be $30/year. This docker downloads the latest release which is currently 20160118atest1

Information Overview: HDHomeRun DVR To install, load the Docker Repository https://github.com/Yoshiofthewire/docker-templates/tree/master/urlxl Requirements: 1) You Need a Silicondust HDHomeRun Tuner 2) You Need to be a Kickstarter backer or buy early access Install: 1) Install the Windows or Mac HDHomeRun DVR to configure your Tuner and run setup to upgraded the firmware. 2) Configure a new Docker Container from the Repository above. 3) The container volume must be /hdhomerun Update: 1) Install the Windows or Mac HDHomeRun DVR to configure your Tuner and run setup to upgrade the firmware. 2) Check and apply updates to update the container. Notes: Current Record Engine Build: 20210501beta1 Current Firmware Build: 20210501beta1

I am getting on of two errors root@evie:/usr/bin# /usr/bin/hdhomerun_record_x86 start bash: /usr/bin/hdhomerun_record_x86: cannot execute binary file: Exec format error root@evie:/usr/bin# sudo /usr/bin/hdhomerun_record_x86 start /usr/bin/hdhomerun_record_x86: 1: /usr/bin/hdhomerun_record_x86: Syntax error: "(" unexpected That said, the log isn't saying anything, because file moves are not working

So I am trying to build a container for hdhomerun dvr and I am completely stumped. I must be doing something wrong. I was using the limetech plex as a template. The install.sh is not running some basic commands. The hdhomerun dvr wont run itself. The container will create and I can install it, but it does nothing. Ideas? https://registry.hub.docker.com/u/yoshiofthewire/hdhomerundvr/

I tried to create TVHdeadend with the following code docker run -d -–name=tvheadend -v /mnt/cache/docker:/config -v /mnt/user/RecordedTV:/recordings -v /etc/localtime:/etc/localtime:ro -p 9981:9981 -p 9982:9982 -p 5004:5004 tobbenb/tvheadend-unstable I can see the container running, but I am unable to connect to the web interface. The page never loads. What did I do wrong?

Issue: Unable to assign drives in unRAID 5.0rc1 in VMware ESXi5 off virtual controllers. In VMware ESXi5 launch unRAID 5.0rc1 with or without VMware tools. Have a virtual HDD assigned to the unRAID VM The HDD fails to show in unRAID with all but the virtual LSI Logic SAS SCSI Controller In unRAID 5.0rc1 the drive shows, but will fail to assign to the array In unRAID 4.7 the drive can be assigned to the array normally. The only change I made was replacing 5.0rc1 on my USB key for 4.7 Is there something I should test? Is there an error I should try to replicate? Is there a log file I need to find? Thanks in Advanced, Matt