Leaderboard

Application Name: TVHeadend Application Site: https://tvheadend.org/ Docker Hub: https://hub.docker.com/r/linuxserver/tvheadend/ Github: https://github.com/linuxserver/docker-tvheadend Please post any questions/issues relating to this docker you have in this thread. **Notes** - Please take a look at the readme's about how the tags work for this docker image. Migration from tobben's TVHeadend docker should work fine but you may need to reconfigure xmltv If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Support for CrashPlan PRO (aka CrashPlan for Small Business) docker container Application Name: CrashPlan PRO (aka CrashPlan for Small Business) Application Site: https://www.crashplan.com/en-us/business/ Docker Hub: https://hub.docker.com/r/jlesage/crashplan-pro/ Github: https://github.com/jlesage/docker-crashplan-pro NOTE ******************************************** If you want to migrate from CrashPlan for Home and are using my CrashPlan container, follow these steps for a smooth transition: Make sure you have migrated your CrashPlan account. Stop the CrashPlan (Home version) container. Login to your unRAID server and copy the app data (the goal being that the new docker re-use the same data): cp -a /mnt/user/appdata/CrashPlan /mnt/user/appdata/CrashPlanPRO Finally, install this container using the Community Applications plugin. After these steps, everything should work like before. Once you are happy with the transition, you can remove the old CrashPlan container and its appdata folder. NOTE: If you are using another container, you can still migrate using this container. See the dedicated section in the documentation for details. ******************************************** This container is based on Alpine Linux, meaning that its size is very small. It also has a very nice, mobile-friendly web UI to access CrashPlan PRO's graphical interface and is actively supported! Make sure to look at the complete documentation, available on Github ! Post any questions or issues relating to this docker in this thread. Warning! Make sure to read the Taking Over Existing Backup section from the documentation if you are installing this container to replace another CrashPlan installation (from Windows, Linux, Mac or even another Docker container).

Set the network adapter to be an E1000 rather than virtio in the XML for the VM. So change: <interface type='bridge'> <mac address='xx:xx:xx:xx:xx:xx'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x0x' slot='0x0x' function='0x0'/> </interface> To this: <interface type='bridge'> <mac address='xx:xx:xx:xx:xx:xx'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x0x' slot='0x0x' function='0x0'/> </interface>

Docker image is corrupt, delete and re-create.

Looks like the backup engine is crashing... How big is your backup? Maybe you need to increase memory.

Have you added --device=/dev/dvb in the extra parameters box in the Tvheadend template?

Take a dump of the syslog for 6.3.5 and then find out what's missing, with regards to the TBS card, from the logs between 6.3.5 and 6.4.x This is how I found out that my Hauppauge card wasn't being detected in the earlier 6.4.x builds by CHBMB, which to do with changes to cx23885 code in v4l. Doing a "modprobe cx23885" in an unRAID ssh session then showed up a few errors that led to a resolution.

so, this has now been done and the image built, in order to use this you will need to create an environment variable called:- ENABLE_AUTODL_IRSSI and set the value to either 'yes' or 'no', if undefined it defaults to 'no' edit - a buget (small bug :-) ) has been found currently rebuilding image...

You'll have to flash it to IT mode if it doesn't come like that. https://forums.lime-technology.com/topic/12114-lsi-controller-fw-updates-irit-modes/ Should be plug and play. But, never hurts to take a screen shot of your drive assignments (and back up the flash drive) just in case the old controller and the new one name the drives slightly differently.

With this now being available, I'm going to deprecate the already existing CrashPlan applications (both of them), with a note that existing installations will cease to work October 2018 and suggest to migrate to Pro or find a different solution