chvb

Does someone have a prebuild 6.3.5 vmdk image? Thanks

Hi Vaseer, this is not needed. You have to configure your nextcloud.

Hello, I've added some Docker Templates: -Webgrabplus -TvhProxy -Collabora/Code

thank you!

For the DVBLink Docker you can now use a Softcam on a Intel System. I've tested it and it works well! Starting from build 14061/14072/14073 (depending on the platform - viewtopic.php?f=55&t=31285) DVBLink TVSource supports new plugin interface, called mdjapi. The plugins are only supported on intel-based platforms - e.g. Windows, Ubuntu, MacOS, all intel-based NAS models.The plugin spec comes from the original acamd author and was recently published here (spec is in English, site is in Dutch):https://www.sat4all.com/forums/topic/23 ... &p=2430476Another group of developers was working on the implementation of mdjapi for DVBLink. I have seen the pre-built binaries on a filedrop site at the following link (I do not know how long they will stay there):http://dropmefiles.com/B47VMThe plugins have to be put into <dvblink share directory>/mirror/sources/<your tvsource source>/plugins.

Great! Thanks for your feedback.

Did you have add the extra Parameters? I use a SatIP Device. There is working everything fine.

After hours of testing the DVBLink Docker is working without Problems. The Config Files are now in the Unraid share so the configuration is consistant. The DVBLink Docker is starting correctly after a restart. Enjoy it.

Hey Page3, the correct URL should be http://IP:9981/play/dvrfile/

hey Saarg, thanks for your suggestion. Now I've moved away from Docker with TvHeadend and created a Ubuntu VM. I've added this to my Syslinux.cfg for my 2 Digital Devices Adapters and installed the stock bzroot+bzimage files. append vfio-pci.ids=dd01:0003 initrd=/bzroot After a reboot i've added the Adapters to a new Ubuntu 16.04 VM and installed TvHeadend and mapped a NFS share for recordings. All 6 Adapters working correctly. Also the recording feature. If anybody have the same issue this is a way you can go.

thanks for your answer. Is there a version which works correctly in the CA? thanks.

Hey together, I've got a Problem with Tvheadend. When I start a recording, the container hangs! I can see this Message in the Log: mpegts: too much queued table input data Until recently the recordings worked. Thanks.

I know.... Why I pumped out an update (2016.11.28b) to prevent the docker updates from running on 6.2.4. The issue has been identified and fixed. Just needs to be tested with the co-operation of lsio. Issue was a very minor difference in the operation of dockerMan on 6.2.4 vs 6.3 (Actually, a bug fix that was implemented on 6.2.0, but the fix didn't make it into dockerMan on the 6.2 series, but was subsequently added to 6.3.x) Hey together, I've still having this issue on 6.3 RC5. Or i understand something wrong?

I've removed /config/channel/config/config.tmp and /config/channel/config/tag.tmp after that, i have removed the backups under /backup after a restart of the container, tvheadend works. I think there was a problem with the migrating of the data to newer version. Thanks for the help!

this is the error from the log. ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/donations/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 2016-10-09 15:47:58.334 [ INFO] main: Log started 2016-10-09 15:47:58.336 [ INFO] http: Starting HTTP server 0.0.0.0:9981 2016-10-09 15:47:58.337 [ INFO] htsp: Starting HTSP server 0.0.0.0:9982 2016-10-09 15:47:58.337 [ ERROR] satips: use --satip_bindaddr parameter to select the local IP for SAT>IP 2016-10-09 15:47:58.337 [ ERROR] satips: using Google lookup (might block the task until timeout) 2016-10-09 15:47:58.369 [ INFO] satips: Starting SAT>IP RTSP server 172.17.0.9:9983 2016-10-09 15:47:58.369 [ INFO] satips: SAT>IP Server initialized 2016-10-09 15:47:58.369 [ INFO] satips: HTTP 172.17.0.9:9981, RTSP 172.17.0.9:9983 2016-10-09 15:47:58.369 [ INFO] satips: descramble 1, muxcnf 0 2016-10-09 15:47:58.395 [ INFO] config: backup: migrating config from 4.1-2249~g747ed01 (running 4.1-2267~g6efcfd2) 2016-10-09 15:47:58.395 [ INFO] config: backup: running, output file /config/backup/4.1-2249~g747ed01.tar.bz2 2016-10-09 15:47:58.395 [ INFO] spawn: Executing "/bin/tar" 2016-10-09 15:48:12.800 [ INFO] config: backup: completed 2016-10-09 15:48:12.815 [ ERROR] START: filename /config/channel/config/config.tmp is invalid 2016-10-09 15:48:12.825 [ INFO] main: Log started 2016-10-09 15:48:12.827 [ INFO] http: Starting HTTP server 0.0.0.0:9981 2016-10-09 15:48:12.828 [ INFO] htsp: Starting HTSP server 0.0.0.0:9982 2016-10-09 15:48:12.828 [ ERROR] satips: use --satip_bindaddr parameter to select the local IP for SAT>IP 2016-10-09 15:48:12.828 [ ERROR] satips: using Google lookup (might block the task until timeout) 2016-10-09 15:48:12.867 [ INFO] satips: Starting SAT>IP RTSP server 172.17.0.9:9983 2016-10-09 15:48:12.867 [ INFO] satips: SAT>IP Server initialized 2016-10-09 15:48:12.867 [ INFO] satips: HTTP 172.17.0.9:9981, RTSP 172.17.0.9:9983 2016-10-09 15:48:12.867 [ INFO] satips: descramble 1, muxcnf 0 2016-10-09 15:48:12.886 [ INFO] config: backup: migrating config from 4.1-2249~g747ed01 (running 4.1-2267~g6efcfd2) 2016-10-09 15:48:12.886 [ INFO] config: backup: running, output file /config/backup/4.1-2249~g747ed01.tar.bz2 2016-10-09 15:48:12.887 [ INFO] spawn: Executing "/bin/tar" 2016-10-09 15:48:27.192 [ INFO] config: backup: completed 2016-10-09 15:48:27.208 [ ERROR] START: filename /config/channel/config/config.tmp is invalid 2016-10-09 15:48:27.219 [ INFO] main: Log started 2016-10-09 15:48:27.221 [ INFO] http: Starting HTTP server 0.0.0.0:9981 2016-10-09 15:48:27.222 [ INFO] htsp: Starting HTSP server 0.0.0.0:9982 2016-10-09 15:48:27.222 [ ERROR] satips: use --satip_bindaddr parameter to select the local IP for SAT>IP 2016-10-09 15:48:27.222 [ ERROR] satips: using Google lookup (might block the task until timeout) 2016-10-09 15:48:27.254 [ INFO] satips: Starting SAT>IP RTSP server 172.17.0.9:9983 2016-10-09 15:48:27.254 [ INFO] satips: SAT>IP Server initialized 2016-10-09 15:48:27.254 [ INFO] satips: HTTP 172.17.0.9:9981, RTSP 172.17.0.9:9983 2016-10-09 15:48:27.254 [ INFO] satips: descramble 1, muxcnf 0 2016-10-09 15:48:27.286 [ INFO] config: backup: migrating config from 4.1-2249~g747ed01 (running 4.1-2267~g6efcfd2) 2016-10-09 15:48:27.286 [ INFO] config: backup: running, output file /config/backup/4.1-2249~g747ed01.tar.bz2 2016-10-09 15:48:27.286 [ INFO] spawn: Executing "/bin/tar"

Hi, i've updated today to the latest Version of TvHeadend. After that, TvHeadend doesn't start up. I don't know the Problem. I've removed the docker image and rolled back to the previous Docker container by running this command: docker run -d --name="tvheadend" --net="bridge" -e TZ="Europe/Berlin" -e HOST_OS="unRAID" -e "PGID"="100" -e "PUID"="99" -p 9981:9981/tcp -p 9982:9982/tcp -v "/mnt/user/appdata/tvheadend":"/config":rw -v "/mnt/user/Aufnahmen/":"/recordings":rw -v "/mnt/user/appdata/tvheadend/logos":"/logos":rw --device=/dev/dvb/ linuxserver/tvheadend:29 Thanks, chvb

Nice to know. Thanks.

please sure you make these steps: 1. Install your DVBDriver with the Plugin of CHMB: http://lime-technology.com/forum/index.php?topic=47899.0 Edit the DVBLInk Docker with Advanced Display and add these Extra Parameters: --device=/dev/dvb Edit your /boot/config/go file and add these line: chown -R nobody:users /dev/dvb & Remember: don't forget to reboot your System:

Some things have to be done to use the DVBLink: 1. Install your DVBDriver with the Plugin of CHMB: http://lime-technology.com/forum/index.php?topic=47899.0 Edit the DVBLInk Docker with Advanced Display and add these Extra Parameters: --device=/dev/dvb Remember: don't forget to reboot your System: If you are using SATIP you have to set the Docker to "Host" mode Network Type: Host Remember: Set the Recording path inside the DVBLink configuration Recording path: /recordings/ DVBLink - DVBAPI - Softcam Starting from build 14061/14072/14073 DVBLink TVSource supports new plugin interface, called mdjapi. The plugins are only supported on intel-based platforms - e.g. Windows, Ubuntu, MacOS, all intel-based NAS models.The plugin spec comes from the original acamd author and was recently published here (spec is in English, site is in Dutch):https://www.sat4all.com/forums/topic/23 ... &p=2430476Another group of developers was working on the implementation of mdjapi for DVBLink. I have seen the pre-built binaries on a filedrop site at the following link (I do not know how long they will stay there):http://dropmefiles.com/B47VMThe plugins have to be put into <dvblink share directory>/mirror/sources/<your tvsource source>/plugins. Some things to the Kerio Connect Docker: If you want to manage the Docker, you can connect to the Docker with Putty / WinSCP Username: Docker PW: test123 //Change your Path for Mailstore inside the Docker / initial setup change it to: /kerio_store // How to update Kerio Docker You have to remove kerio files/folders in your volume but keep this follow files/folder: (The docker will copy the missing Files) *.cfg mailserver/store mailserver/dbSSL mailserver/license mailserver/settings mailserver/sslca mailserver/sslcert mailserver/ldapmap // How can i Replace a Backup? // Log into SSH and Replace Backup sudo service kerio-connect stop sudo /opt/kerio/mailserver/kmsrecover /backup sudo service kerio-connect start

Support thread for: Docker Container: -DVBLink -Kerio Connect -Apache-PHP -Webgrabplus -TVHProxy Template: -Collabora/Code Repository: https://github.com/chvb/docker-templates Docker Hub: https://hub.docker.com/u/chvb/ GitHub: https://github.com/chvb

Hey, thanks for this Information. I'm using Emby. The same thing here. Maybe you can change the Topic: Plex/Emby: Guide to Moving Transcoding to RAM Many thanks

+1 iSCSI feature for the cache pool would be so nice

thanks for the Update. Its working fine for me.

Thanks for the update

Hey Mettbrot, thanks for the latest update.